You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cassandra.apache.org by Jinhua Luo <lu...@gmail.com> on 2018/04/28 10:10:47 UTC
what happens for concurrent node add/removal?
HI All,
For example, if at the same time, two nodes joining and there nodes removing.
How c* handles such case? c* uses gossip to determine membership, and
it does not have central leader to serialize the membership changes.
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@cassandra.apache.org
For additional commands, e-mail: user-help@cassandra.apache.org
Re: what happens for concurrent node add/removal?
Posted by Jeff Jirsa <jj...@gmail.com>.
The second node will fail to start because of concurrent movement concerns
There’s a flag to override this if you know when it’s safe (for advanced users only)
--
Jeff Jirsa
> On Apr 28, 2018, at 3:10 AM, Jinhua Luo <lu...@gmail.com> wrote:
>
> HI All,
>
> For example, if at the same time, two nodes joining and there nodes removing.
> How c* handles such case? c* uses gossip to determine membership, and
> it does not have central leader to serialize the membership changes.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@cassandra.apache.org
> For additional commands, e-mail: user-help@cassandra.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@cassandra.apache.org
For additional commands, e-mail: user-help@cassandra.apache.org
Re: what happens for concurrent node add/removal?
Posted by Nitan Kainth <ni...@gmail.com>.
Seed node takes care of token re-assignment. But why do you even wanna do that? Add the node first and then remove.
Sent from my iPhone
> On Apr 28, 2018, at 5:10 AM, Jinhua Luo <lu...@gmail.com> wrote:
>
> HI All,
>
> For example, if at the same time, two nodes joining and there nodes removing.
> How c* handles such case? c* uses gossip to determine membership, and
> it does not have central leader to serialize the membership changes.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@cassandra.apache.org
> For additional commands, e-mail: user-help@cassandra.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@cassandra.apache.org
For additional commands, e-mail: user-help@cassandra.apache.org