Re: Totally unbalanced cluster

Hi, Regarding the documentation I've already knew: - thelastpickle.com/blog/2016/07/27/about-deletes-and-tombstones.html (From myself, how to handle tombstones) - http://thelastpickle.com/blog/2016/12/08/TWCS-part1.html

Re: Totally unbalanced cluster

Hi, > but it's so easy to add nodes Apache Cassandra has some kind of magic pieces ;-). Sometimes it is dark magic though :p. Yet adding a node is indeed not harder when using NetworkTopologyStrategy, as Jon mentioned above, once the configuration is done once properly. > Number of keys

Re: Totally unbalanced cluster

Adding nodes with NTS is easier, in my opinion. You don’t need to worry about replica placement, if you do it right. > On May 4, 2017, at 7:43 AM, Cogumelos Maravilha > wrote: > > Hi Alain thanks for your kick reply. > > > Regarding SimpleStrategy perhaps you

Re: Totally unbalanced cluster

Hi Alain thanks for your kick reply. Regarding SimpleStrategy perhaps you are right but it's so easy to add nodes. I'm *not* using vnodes and the default 256. The information that I've posted it a regular nodetool status keyspace. My partition key is a sequencial big int but nodetool cfstatus

Re: Totally unbalanced cluster

Hi, CREATE KEYSPACE mykeyspace WITH replication = {'class': > 'SimpleStrategy', 'replication_factor': '2'} AND durable_writes = false; The SimpleStrategy is never recommended for production clusters as it does not recognise racks or datacenter, inducing possible availability issues and

Totally unbalanced cluster

Hi all, I'm using C* 3.10. CREATE KEYSPACE mykeyspace WITH replication = {'class': 'SimpleStrategy', 'replication_factor': '2'} AND durable_writes = false; CREATE TABLE mykeyspace.data ( id bigint PRIMARY KEY, kafka text ) WITH bloom_filter_fp_chance = 0.5 AND caching = {'keys':