Re: Multiple nodes decommission

2017-04-20 Thread Vlad
>There's a system property (actually 2)Which ones? On Wednesday, April 19, 2017 9:17 AM, Jeff Jirsa wrote: On 2017-04-12 11:30 (-0700), Vlad wrote: > Interesting, there is no such explicit warning for v.3 >

Re: Multiple nodes decommission

2017-04-19 Thread Jeff Jirsa
On 2017-04-12 11:30 (-0700), Vlad wrote: > Interesting, there is no such explicit warning for v.3 > https://docs.datastax.com/en/cassandra/3.0/cassandra/operations/opsAddNodeToCluster.html > It says >- Start the bootstrap node. >- verify that the node is fully

Re: Multiple nodes decommission

2017-04-16 Thread Jens Rantil
AFAIK, the fastest way to add multiple nodes is to make sure your clients are only reading/writing to/from your current datacenter, create a new datacenter with replication 0, add nodes to the new datacenter, increase replication factor of the new datacenter, do `nodetool bootstrap` on all nodes

Re: Multiple nodes decommission

2017-04-15 Thread Vlad
>range reassignments which becomes effective after a successful decommission. But during leaving nodes announce themselves as "leaving". Do other leaving nodes taking this into account and not stream data to them? (applicable also for joining). I hope so )) I guess problem with sequential

Re: Multiple nodes decommission

2017-04-12 Thread Vlad
Interesting, there is no such explicit warning for v.3 https://docs.datastax.com/en/cassandra/3.0/cassandra/operations/opsAddNodeToCluster.html It says - Start the bootstrap node. - verify that the node is fully bootstrapped and all other nodes are up (UN) Does it mean that we should

Re: Multiple nodes decommission

2017-04-12 Thread Jacob Shadix
It's still not recommended to start at the same time. Stagger by 2 minutes is what the following documentation suggests; along with additional steps. re. version 2.1 https://docs.datastax.com/en/cassandra/2.1/cassandra/operations/ops_add_node_to_cluster_t.html -- Jacob Shadix On Wed, Apr 12,

Re: Multiple nodes decommission

2017-04-12 Thread Vlad
But it seems OK to add multiple nodes at once, right? On Tuesday, April 11, 2017 8:38 PM, Jacob Shadix wrote: Right! Another reason why I just stick with sequential decommissions. Maybe someone here could shed some light on what happens under the covers if

Re: Multiple nodes decommission

2017-04-11 Thread Jacob Shadix
Right! Another reason why I just stick with sequential decommissions. Maybe someone here could shed some light on what happens under the covers if parallel decommissions are kicked off. -- Jacob Shadix On Tue, Apr 11, 2017 at 12:55 PM, benjamin roth wrote: > I did not test it

Re: Multiple nodes decommission

2017-04-11 Thread benjamin roth
I did not test it but I'd bet that parallel decommision will lead to inconsistencies. Each decommission results in range movements and range reassignments which becomes effective after a successful decommission. If you start several decommissions at once, I guess the calculated reassignments are

Re: Multiple nodes decommission

2017-04-11 Thread Jacob Shadix
Are you using vnodes? I typically do one-by-one as the decommission will create additional load/network activity streaming data to the other nodes as the token ranges are reassigned. -- Jacob Shadix On Sat, Apr 8, 2017 at 10:55 AM, Vlad wrote: > Hi, > > how multiple nodes