Re: Re[6]: Modify keyspace replication strategy and rebalance the nodes

2017-09-19 Thread Jeff Jirsa
; Sincerely, > > Myron A. Semack > > > > *From:* Jeff Jirsa [mailto:jji...@gmail.com] > *Sent:* Monday, September 18, 2017 6:02 PM > *To:* cassandra > > *Subject:* Re: Re[6]: Modify keyspace replication strategy and rebalance > the nodes > > > > Using C

RE: Re[6]: Modify keyspace replication strategy and rebalance the nodes

2017-09-19 Thread Myron A. Semack
satisfied)? Sincerely, Myron A. Semack From: Jeff Jirsa [mailto:jji...@gmail.com] Sent: Monday, September 18, 2017 6:02 PM To: cassandra Subject: Re: Re[6]: Modify keyspace replication strategy and rebalance the nodes Using CL:ALL basically forces you to always include the first replica in the

Re: Re[6]: Modify keyspace replication strategy and rebalance the nodes

2017-09-18 Thread kurt greaves
So I haven't completely thought through this, so don't just go ahead and do it. Definitely test first. Also if anyone sees something terribly wrong don't be afraid to say. Seeing as you're only using SimpleStrategy and it doesn't care about racks, you could change to SimpleSnitch, or GossipingProp

Re: Re[6]: Modify keyspace replication strategy and rebalance the nodes

2017-09-18 Thread Jeff Jirsa
sandra.apache.org > *Subject:* Re: Re[6]: Modify keyspace replication strategy and rebalance > the nodes > > > > The hard part here is nobody's going to be able to tell you exactly what's > involved in fixing this because nobody sees your ring > > > > And

RE: Re[6]: Modify keyspace replication strategy and rebalance the nodes

2017-09-18 Thread Myron A. Semack
: Re: Re[6]: Modify keyspace replication strategy and rebalance the nodes The hard part here is nobody's going to be able to tell you exactly what's involved in fixing this because nobody sees your ring And since you're using vnodes and have a nontrivial number of instances, sharing

Re: Re[6]: Modify keyspace replication strategy and rebalance the nodes

2017-09-18 Thread Jeff Jirsa
The hard part here is nobody's going to be able to tell you exactly what's involved in fixing this because nobody sees your ring And since you're using vnodes and have a nontrivial number of instances, sharing that ring (and doing anything actionable with it) is nontrivial. If you weren't usin