Hi,
I finally successfully removed the "ghost" node using
unsafeAssassinateEndpoint() as described there :
http://tumblr.doki-pen.org/post/22654515359/assinating-cassandra-nodes,
I hope this can help more people.
Nodetool gossipinfo gives me now the following info for the ghost node :
/10.56.62.211
RELEASE_VERSION:1.1.2
RPC_ADDRESS:0.0.0.0
REMOVAL_COORDINATOR:REMOVER,85070591730234615865843651857942052864
SCHEMA:59adb24e-f3cd-3e02-97f0-5b395827453f
STATUS:LEFT,42529904547457370790386101505459979624,1344611213445
LOAD:11594.0
DC:eu-west
RACK:1b
Instead of :
/10.56.62.211
RELEASE_VERSION:1.1.2
LOAD:11594.0
RACK:1b
SCHEMA:59adb24e-f3cd-3e02-97f0-5b395827453f
DC:eu-west
REMOVAL_COORDINATOR:REMOVER,85070591730234615865843651857942052864
STATUS:removed,170141183460469231731687303715884105727,1342453967415
RPC_ADDRESS:0.0.0.0
Cassandra-cli describe cluster now don't show me any unreachable node.
The only issue that remains is that my nodes aren't well load balanced
yet... After repairing, cleaning up, restarting all nodes I still have
the following ring :
Address DC Rack Status State Load
Owns Token
85070591730234615865843651857942052864
10.59.21.241 eu-west 1b Up Normal 103.19 GB
50.00% 0
10.58.83.109 eu-west 1b Up Normal 62.62 GB
50.00% 85070591730234615865843651857942052864
Any idea on why I can't get the load well balanced in this cluster ?
Alain
