Re: How long/how many days 'nodetool gossipinfo' will have decommissioned nodes info

2016-09-28 Thread Alain RODRIGUEZ 
>
> 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,
---
Alain Rodriguez - @arodream - al...@thelastpickle.com
France

The Last Pickle - Apache Cassandra Consulting
http://www.thelastpickle.com

2016-09-26 21:17 GMT+02:00 laxmikanth sadula :

> 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:
>>
>>> 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. On larger
>>> clusters, running this command synchronously across all machines may be
>>> required. Instructions on Assassinate Endpoint can be found here:
>>>
>>> https://gist.github.com/justenwalker/8338334
>>>
>>> If you're planning on recommissioning the same node, upon bootstrapping
>>> the gossiped message should change to a JOINING message overwriting the
>>> LEFT message.
>>>
>>> I've personally never checked `nodetool gossipinfo` before
>>> recommissioning a node and typically only ensure the node does not appear
>>> in `nodetool status`.
>>>
>>> Hope that helps,
>>>
>>> Joaquin Casares
>>> Consultant
>>> Austin, TX
>>>
>>> Apache Cassandra Consulting
>>> http://www.thelastpickle.com
>>>
>>> On Sun, Sep 25, 2016 at 2:17 PM, Laxmikanth S 
>>> wrote:
>>>
 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 node(same IP)
  again while its state is maintained as LEFT in 'nodetool gossipnfo'.


 Thanks,
 Techpyaasa

>>>
>>>
>>
>
>
> --
> Regards,
> Laxmikanth
> 99621 38051
>
>

Re: How long/how many days 'nodetool gossipinfo' will have decommissioned nodes info

2016-09-26 Thread laxmikanth sadula 
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:
>
>> 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. On larger
>> clusters, running this command synchronously across all machines may be
>> required. Instructions on Assassinate Endpoint can be found here:
>>
>> https://gist.github.com/justenwalker/8338334
>>
>> If you're planning on recommissioning the same node, upon bootstrapping
>> the gossiped message should change to a JOINING message overwriting the
>> LEFT message.
>>
>> I've personally never checked `nodetool gossipinfo` before
>> recommissioning a node and typically only ensure the node does not appear
>> in `nodetool status`.
>>
>> Hope that helps,
>>
>> Joaquin Casares
>> Consultant
>> Austin, TX
>>
>> Apache Cassandra Consulting
>> http://www.thelastpickle.com
>>
>> On Sun, Sep 25, 2016 at 2:17 PM, Laxmikanth S 
>> wrote:
>>
>>> 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 node(same IP)
>>>  again while its state is maintained as LEFT in 'nodetool gossipnfo'.
>>>
>>>
>>> Thanks,
>>> Techpyaasa
>>>
>>
>>
>


-- 
Regards,
Laxmikanth
99621 38051

Re: How long/how many days 'nodetool gossipinfo' will have decommissioned nodes info

2016-09-26 Thread DuyHai Doan 
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 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. On larger
> clusters, running this command synchronously across all machines may be
> required. Instructions on Assassinate Endpoint can be found here:
>
> https://gist.github.com/justenwalker/8338334
>
> If you're planning on recommissioning the same node, upon bootstrapping
> the gossiped message should change to a JOINING message overwriting the
> LEFT message.
>
> I've personally never checked `nodetool gossipinfo` before recommissioning
> a node and typically only ensure the node does not appear in `nodetool
> status`.
>
> Hope that helps,
>
> Joaquin Casares
> Consultant
> Austin, TX
>
> Apache Cassandra Consulting
> http://www.thelastpickle.com
>
> On Sun, Sep 25, 2016 at 2:17 PM, Laxmikanth S 
> wrote:
>
>> 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 node(same IP)  again
>> while its state is maintained as LEFT in 'nodetool gossipnfo'.
>>
>>
>> Thanks,
>> Techpyaasa
>>
>
>

Re: How long/how many days 'nodetool gossipinfo' will have decommissioned nodes info

2016-09-26 Thread Joaquin Casares 
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. On larger
clusters, running this command synchronously across all machines may be
required. Instructions on Assassinate Endpoint can be found here:

https://gist.github.com/justenwalker/8338334

If you're planning on recommissioning the same node, upon bootstrapping the
gossiped message should change to a JOINING message overwriting the LEFT
message.

I've personally never checked `nodetool gossipinfo` before recommissioning
a node and typically only ensure the node does not appear in `nodetool
status`.

Hope that helps,

Joaquin Casares
Consultant
Austin, TX

Apache Cassandra Consulting
http://www.thelastpickle.com

On Sun, Sep 25, 2016 at 2:17 PM, Laxmikanth S  wrote:

> 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 node(same IP)  again
> while its state is maintained as LEFT in 'nodetool gossipnfo'.
>
>
> Thanks,
> Techpyaasa
>

How long/how many days 'nodetool gossipinfo' will have decommissioned nodes info

2016-09-25 Thread Laxmikanth S 
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 node(same IP)  again
while its state is maintained as LEFT in 'nodetool gossipnfo'.


Thanks,
Techpyaasa