You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "pavel (JIRA)" <ji...@apache.org> on 2016/02/15 10:18:18 UTC

[jira] [Comment Edited] (CASSANDRA-10371) Decommissioned nodes can remain in gossip

    [ https://issues.apache.org/jira/browse/CASSANDRA-10371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15144713#comment-15144713 ] 

pavel edited comment on CASSANDRA-10371 at 2/15/16 9:18 AM:
------------------------------------------------------------

Exactly the same was reproduced in 2.1.11
Could you please reopen the ticket?
I have the cluster in this state up and running and I can 
give you all the necessary logs.



was (Author: pontryagin):
Exactly the same was reproduced in 2.1.11

> Decommissioned nodes can remain in gossip
> -----------------------------------------
>
>                 Key: CASSANDRA-10371
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10371
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Distributed Metadata
>            Reporter: Brandon Williams
>            Assignee: Stefania
>            Priority: Minor
>
> This may apply to other dead states as well.  Dead states should be expired after 3 days.  In the case of decom we attach a timestamp to let the other nodes know when it should be expired.  It has been observed that sometimes a subset of nodes in the cluster never expire the state, and through heap analysis of these nodes it is revealed that the epstate.isAlive check returns true when it should return false, which would allow the state to be evicted.  This may have been affected by CASSANDRA-8336.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)