Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Sun, 4 Sep 2011 01:53:09 +0000 (UTC)
From: =?utf-8?Q?J=C3=A9r=C3=A9my_Sevellec_=28JIRA=29?= <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <2165729.15379.1315101189988.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <19775072.14086.1311808989714.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (CASSANDRA-2961) Expire dead gossip states based
 on time
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/CASSANDRA-2961?page=3Dcom.atla=
ssian.jira.plugin.system.issuetabpanels:all-tabpanel ]

J=C3=A9r=C3=A9my Sevellec updated CASSANDRA-2961:
---------------------------------------

    Comment: was deleted

(was: here is the patch)

> Expire dead gossip states based on time
> ---------------------------------------
>
>                 Key: CASSANDRA-2961
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2961
>             Project: Cassandra
>          Issue Type: Improvement
>    Affects Versions: 1.0
>            Reporter: Brandon Williams
>              Labels: patch
>             Fix For: 1.0
>
>
> Currently dead states are held until aVeryLongTime, 3 days.  The problem =
is that if a node reboots within this period, it begins a new 3 days and wi=
ll repopulate the ring with the dead state.  While mostly harmless, perpetu=
ating the state forever is at least wasting a small amount of bandwidth.  I=
nstead, we can expire states based on a ttl, which will require that the cl=
uster be loosely time synced; within the quarantine period of 60s.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira