Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 18 Sep 2015 00:44:04 +0000 (UTC)
From: "Brandon Williams (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12875742.1442536936000.7022.1442537044202@Atlassian.JIRA>
In-Reply-To: <JIRA.12875742.1442536936000@Atlassian.JIRA>
References: <JIRA.12875742.1442536936000@Atlassian.JIRA>
 <JIRA.12875742.1442536936696@arcas>
Subject: [jira] [Updated] (CASSANDRA-10371) Decommissioned nodes can remain
 in gossip
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CASSANDRA-10371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brandon Williams updated CASSANDRA-10371:
-----------------------------------------
    Reproduced In: 2.0.16

> Decommissioned nodes can remain in gossip
> -----------------------------------------
>
>                 Key: CASSANDRA-10371
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10371
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Brandon Williams
>            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)