Hello,
I have several questions about decommissioned nodes that I would like
to clarify:
- What happens in Cassandra with a failed node that has been
decommissioned if it returns to the cluster with old data and its old
token?
- Will it actualize the data using ReadRepair or the bootstrapping
- What happens in Cassandra with a failed node that has been
decommissioned if it returns to the cluster with old data and its old
token?
If it starts normally it *may* take ownership of the token away from the
previous node. The Gossip Generation is compared and the server with the higher
Sorry, got that a little wrong.
At startup the node will use the higher of the current seconds since epoch or
the stored generation number.
So if you restart the old node it should always take ownership of it's token.
Cheers
-
Aaron Morton
Freelance Developer
@aaronmorton
On Tue, Dec 20, 2011 at 2:24 PM, aaron morton aa...@thelastpickle.com wrote:
Sorry, got that a little wrong.
At startup the node will use the higher of the current seconds since epoch
or the stored generation number.
Technically stored generation + 1 so it's always increased on a restart.
What happens with the data stored for that token range already in the
cluster? will the restarted node actualize it from any of the
replicas?
I readed in the maillist archives that in case of token collision, the
cluster may not work correctly. But if the restarted node takes always
ownership of
A node will only request data from other nodes on start up if it is
bootstrapping. Bootstrapping happens when there is no system data and the
auto_bootstrap: yaml config is set true, normally nodes only bootstrap once in
their life.
If you bring a node back for whatever reason you will want
