Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 29 Jul 2014 20:44:40 +0000 (UTC)
From: "Brandon Williams (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12532274.1321941686584.69075.1406666680111@arcas>
In-Reply-To: <JIRA.12532274.1321941686584@arcas>
References: <JIRA.12532274.1321941686584@arcas>
Subject: [jira] [Updated] (CASSANDRA-3516) Make bootstrapping smarter
 instead of using 120 seconds to stabilize the ring
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Brandon Williams updated CASSANDRA-3516:
----------------------------------------

    Fix Version/s:     (was: 2.1.1)

> Make bootstrapping smarter instead of using 120 seconds to stabilize the ring
> -----------------------------------------------------------------------------
>
>                 Key: CASSANDRA-3516
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3516
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 1.0.2
>            Reporter: Chris Goffinet
>
> We run a very large cluster, and the 120s doesn't really make sense. We see gossip take anywhere from 30 to 60 seconds for the ring to actually mark nodes up or down (stabilize). We need to come up with a better way instead of picking an arbitrary number to wait. Our clusters are growing so large where 120s won't be enough time.


--
This message was sent by Atlassian JIRA
(v6.2#6252)