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

2017-09-14 Thread kurt greaves
Sorry that only applies our you're using NTS. You're right that simple strategy won't work very well in this case. To migrate you'll likely need to do a DC migration to ensuite no downtime, as replica placement will change even if RF stays the same. On 15 Sep. 2017 08:26, "kurt greaves" wrote: >

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

2017-09-14 Thread kurt greaves
If you have racks configured and lose nodes you should replace the node with one from the same rack. You then need to repair, and definitely don't decommission until you do. Also 40 nodes with 256 vnodes is not a fun time for repair. On 15 Sep. 2017 03:36, "Dominik Petrovic" wrote: > @jeff, > I

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

2017-09-14 Thread Dominik Petrovic
@jeff, I'm using 3 availability zones, during the life of the cluster we lost nodes, retired others and we end up having some of the data written/replicated on a single availability zone. We saw it with nodetool getendpoints. RegardsĀ  >Thursday, September 14, 2017 9:23 AM -07:00 from Jeff Jirsa