Also, note that repairs will be slower for larger rows and AFAIK also require slightly more memory. Also, to avoid many tombstones it could be worth to consider bucketing your partitions by time.
Cheers, Jens On Fri, Feb 27, 2015 at 7:44 AM, wateray <wate...@163.com> wrote: > Hi all, > My team is using Cassandra as our database. We have one question as below. > As we know, the row with the some partition key will be stored in the some > node. > But how many rows can one partition key hold? What is it depend on? The > node's volume or partition data size or partition rows size(the number of > rows)? > When one partition's data is extreme large, the write/read will slow? > Can anyone show me some exist usecases. > thanks! > > > > > > -- Jens Rantil Backend engineer Tink AB Email: jens.ran...@tink.se Phone: +46 708 84 18 32 Web: www.tink.se Facebook <https://www.facebook.com/#!/tink.se> Linkedin <http://www.linkedin.com/company/2735919?trk=vsrp_companies_res_photo&trkInfo=VSRPsearchId%3A1057023381369207406670%2CVSRPtargetId%3A2735919%2CVSRPcmpt%3Aprimary> Twitter <https://twitter.com/tink>
