"try assasinate from the jmx?
http://nartax.com/2012/09/assassinate-cassandra-node/";
I finally used this solution... It always solves the problems of ghost
nodes :D. Last time I had unreachable nodes while describing cluster in CLI
(as described in the link) and I us
try assasinate from the jmx?
http://nartax.com/2012/09/assassinate-cassandra-node/
or try cassandra -Dcassandra.load_ring_state=false
http://www.datastax.com/docs/1.0/references/cassandra#options
On Tue, Mar 5, 2013 at 6:54 PM, Alain RODRIGUEZ wrote:
> Any clue on this ?
>
>
> 2013/2/25 Alain
Any clue on this ?
2013/2/25 Alain RODRIGUEZ
> Hi,
>
> I am having issues after decommissioning 3 nodes one by one of my 1.1.6 C*
> cluster (RF=3):
>
> On the "c.164" node, which was added a week after removing the 3 nodes,
> with gossipinfo I have:
>
> /a.135
> RPC_ADDRESS:0.0.0.0
> STATU
