cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vlad <>
Subject Re: Multiple nodes decommission
Date Wed, 12 Apr 2017 18:30:29 GMT
Interesting, there is no such explicit warning for v.3
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 start them one by one? May somebody from developers can clarify
this issue? 

    On Wednesday, April 12, 2017 9:16 PM, Jacob Shadix <> wrote:

 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

-- Jacob Shadix 

On Wed, Apr 12, 2017 at 1:48 PM, Vlad <> wrote:

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 parallel decommissions are kicked
-- Jacob Shadix 

On Tue, Apr 11, 2017 at 12:55 PM, benjamin roth <> wrote:

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 invalid for at least one node after the first node finished the decommission
I hope someone will correct me if i am wrong.
2017-04-11 18:43 GMT+02:00 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:

how multiple nodes should be decommissioned by "nodetool decommission"- one by one or in parallel



View raw message