Hey all,
OK I gave removing the downed node from the cassandra ring another try.
To recap what's going on, this is what my ring looks like with nodetool
status:
[root@beta-new:~] #nodetool status
Datacenter: datacenter1
===
Status=Up/Down
|/
One of the nodes in a cassandra cluster has died.
I'm using cassandra 2.0.7 throughout.
When I do a nodetool status this is what I see (real addresses have been
replaced with fake 10 nets)
[root@beta-new:/opt] #nodetool status
Datacenter: datacenter1
===
Assuming replication factor is 2, if a node dies, why does it matter? If
we add a new node is added, shouldn't it just take the chunk of data it
server as the primary node from the other existing nodes.
Why do we need to worry about replacing the dead node?
The reason this matters is
2014, at 17:35, Curious Patient mongoma...@gmail.com wrote:
Assuming replication factor is 2, if a node dies, why does it matter? If
we add a new node is added, shouldn't it just take the chunk of data it
server as the primary node from the other existing nodes.
Why do we need to worry about
10.10.1.98 | head -1
I want to be sure I'm using the right token.
Thanks
Tim
On Tue, Jun 3, 2014 at 1:45 PM, Robert Coli rc...@eventbrite.com wrote:
On Tue, Jun 3, 2014 at 8:41 AM, Curious Patient mongoma...@gmail.com
wrote:
I then started following this documentation on how to replace
, Curious Patient mongoma...@gmail.com
wrote:
I want to be sure I'm using the right token.
In nodetool ring, if you're not using vnodes, only one token should be
listed with both the IP of the old node and the status Down.
If you are using vnodes, it's a comma delimited list in initial_token
