cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tomas Vondra ...@fuzzy.cz>
Subject decommissioning a wrong node
Date Sat, 23 Apr 2011 23:46:04 GMT
Hi all,

I've set up a ring with three nodes to play with. I've tried to
decommision a node, but it seems a different node is decommisioned.

Example - the nodes are running:

~/cassandra $ nodetool -h 10.0.0.1 ring
Address    Status State  Load     Owns    Token
                                          729261389019385599444...
10.0.0.3   Up     Normal 62,28 KB 72,05%  253757231779485488680...
10.0.0.1   Up     Normal 53,67 KB 25,16%  681842499981089716433...
10.0.0.2   Up     Normal 57,92 KB 2,79%   729261389019385599444...

And then I would like to decommission node with IP 10.0.0.2, so I do this

~/cassandra $ nodetool -h 10.0.0.2 decommission

which for some reason does this:

 ~/cassandra $ nodetool -h 10.0.0.1 ring
Address    Status State   Load      Owns    Token
                                            7292613890193855994...
10.0.0.3   Up     Normal  62,28 KB  72,05%  2537572317794854886...
10.0.0.1   Up     Leaving 53,67 KB  25,16%  6818424999810897164...
10.0.0.2   Up     Normal  57,92 KB  2,79%   7292613890193855994...

and in the end

~/cassandra $ nodetool -h 10.0.0.1 ring
Address    Status State   Load      Owns    Token
                                            7292613890193855994...
10.0.0.3   Up     Normal  62,28 KB  72,05%  2537572317794854886...
10.0.0.2   Up     Normal  57,92 KB  27,95%  7292613890193855994...

So a different node (with IP 10.0.0.1, not 10.0.0.2) is decommissioned.


BTW all the nodes are running on the same machine and are set up using
virtual IPs. Not sure if this is important (I don't think it should).

regards
Tomas

Mime
View raw message