>
> I've read from some that the gossip info will stay
> around for 72h before being removed.
>
I've read this one too :-). It is 3 days indeed.
This might be of some interest:
https://issues.apache.org/jira/browse/CASSANDRA-10371 (Fix Version/s:
2.1.14, 2.2.6, 3.0.4, 3.4)
C*heers,
Thank you @Jaoquin and @DuyHai
On Mon, Sep 26, 2016 at 10:00 PM, DuyHai Doan wrote:
> I've read from some that the gossip info will stay
> around for 72h before being removed.
>
> On Mon, Sep 26, 2016 at 6:19 PM, Joaquin Casares <
> joaq...@thelastpickle.com> wrote:
>
>>
I've read from some that the gossip info will stay
around for 72h before being removed.
On Mon, Sep 26, 2016 at 6:19 PM, Joaquin Casares
wrote:
> Hello Techpyassa,
>
> Sometimes old gossip information tends to echo around for quite a bit
> longer than intended. I'm
Hello Techpyassa,
Sometimes old gossip information tends to echo around for quite a bit
longer than intended. I'm unsure how long the LEFT messages are supposed to
be echoed for, but if you want to force the removal of a removed node from
gossip, you can use the Assassinate Endpoint JMX command.
Hi,
Recently we have decommissioned nodes from Cassandra cluster , but even
after nearly 48 hours 'nodetool gossipinfo' still shows the removed nodes(
as LEFT).
I just wanted to recommission the same node again. So just wanted to know ,
will it create a problem if I recommission the same