Hi,
One more thing to consider is wide partition. Even though theoretically
Cassandra supports wide rows, practical limit is max 100 MB per partition.
So based on your use-case and model, you may have to split the data into
partitions so that wide partitions are not created.
Regards,
Firdousi
By "partitions" I assume you refer to "partition keys".
Generally, the more partitions keys, the better. Having more partition keys
means your data generally is spread out more evenly across the cluster,
makes repairs run faster (or so I've heard), makes adding new nodes more
smooth, and makes it
assandra.apache.org>
Date: Wednesday, September 21, 2016 at 2:40 PM
To: "user@cassandra.apache.org" <user@cassandra.apache.org>
Subject: understanding partitions and # of nodes
Hello,
If you have a 10 node cluster, how does having 10 partitions or 100 partitions
change h
Hello,
If you have a 10 node cluster, how does having 10 partitions or 100
partitions change how cassandra will perform?
With 10 partitions you will have 1 partition per node.
WIth 100 partitions you will have 10 partitions per node.
With 100 partitions I guess it helps because when you add
Hello,
If you have a 10 node cluster, how does having 10 partitions or 100
partitions change how cassandra will perform?
With 10 partitions you will have 1 partition per node.
WIth 100 partitions you will have 10 partitions per node.
With 100 partitions I guess it helps because when you add
