M
> To: "user@cassandra.apache.org"
> Subject: Re: auto_boorstrap when a node is down
>
> If that's your use case I've developed a quick disk based replacement
> procedure.
>
> Basically all it involves is rsyncing the data from the old node to the
> ne
e.org>>
Date: Thursday, March 31, 2016 at 10:31 AM
To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>"
mailto:user@cassandra.apache.org>>
Subject: Re: auto_boorstrap when a node is down
If that's your use case I've developed a quick disk based r
dra.apache.org"
> Date: Wednesday, March 30, 2016 at 10:55 AM
> To: "user@cassandra.apache.org"
> Subject: Re: auto_boorstrap when a node is down
>
> When you add a node it will take over the range of an existing node, and
> thus it should stream data from it to maintain con
r@cassandra.apache.org>>
Date: Wednesday, March 30, 2016 at 10:55 AM
To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>"
mailto:user@cassandra.apache.org>>
Subject: Re: auto_boorstrap when a node is down
When you add a node it will take over the range of an e
When you add a node it will take over the range of an existing node, and
thus it should stream data from it to maintain consistency. If the existing
node is unavailable, the new node may fetch the data from a different
replica, which may not have some of data from the node which you are taking
the
Hello all,
We just upgraded to 2.2.4 (from 2.0.9) and we noticed one issue when new nodes
are added. When we add a new node when no nodes are down in the cluster,
everything works fine but when we add new node while 1 node is down, I am
seeing following error. My understanding was when auto_boot
