[
https://issues.apache.org/jira/browse/CASSANDRA-10371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15068180#comment-15068180
]
Stefania commented on CASSANDRA-10371:
--------------------------------------
[~brandon.williams] is this still an issue in 2.1 HEAD? If so can you provide
some log files, ideally at TRACE level or some instructions on how to reproduce
this?
>From a code inspection of 2.1, I could not see anything that would cause
>{{epState.isAlive()}} to be true for a decommissioned node, even taking
>CASSANDRA-8336 into account, a decommissioned node should be in state left and
>it should have been marked as dead.
> 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)
