Re: Is it *safe* to issue multiple replace-node at the same time?

[Paulo Motta]

It's safe but since the replacement node will stream data from a single
replica per local range, it will potentially propagate any inconsistencies
from the replica it streams from, so it's recommended to run repair after a
replace to reduce entropy specially when replacing a node with the same IP
due to CASSANDRA-12344.

2016-11-21 20:34 GMT-02:00 kurt Greaves :

>
> On 21 November 2016 at 18:58, Ben Bromhead  wrote:
>
>> Same rack and no range movements, my first instinct is to say yes it is
>> safe (I like to treat racks as one giant meta node). However I would want
>> to have a read through the replace code.
>
>
> This is assuming RF<=# of racks as well (and NTS).
>
> Kurt Greaves
> www.instaclustr.com
>

Re: Is it *safe* to issue multiple replace-node at the same time?

[kurt Greaves]

On 21 November 2016 at 18:58, Ben Bromhead  wrote:

> Same rack and no range movements, my first instinct is to say yes it is
> safe (I like to treat racks as one giant meta node). However I would want
> to have a read through the replace code.


This is assuming RF<=# of racks as well (and NTS).

Kurt Greaves
www.instaclustr.com

Re: Is it *safe* to issue multiple replace-node at the same time?

[Ben Bromhead]

Same rack and no range movements, my first instinct is to say yes it is
safe (I like to treat racks as one giant meta node). However I would want
to have a read through the replace code.

On Mon, Nov 21, 2016, 07:22 Dikang Gu  wrote:

> Hi guys,
>
> Sometimes we need to replace multiple hosts in the same rack, is it safe
> to replace them in parallel, using the replace-node command?
>
> Will it cause any data inconsistency if we do so?
>
> Thanks
> Dikang.
>
> --
> Dikang
>
> --
Ben Bromhead
CTO | Instaclustr 
+1 650 284 9692
Managed Cassandra / Spark on AWS, Azure and Softlayer