Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Thu, 8 Mar 2012 22:37:57 +0000 (UTC)
From: "Brandon Williams (Commented) (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: 
 <2146987286.40935.1331246277319.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1402110837.34040.1322807019900.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (CASSANDRA-3555) Bootstrapping to handle more
 failure
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Brandon Williams commented on CASSANDRA-3555:
---------------------------------------------

+1 otherwise
                
> Bootstrapping to handle more failure
> ------------------------------------
>
>                 Key: CASSANDRA-3555
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3555
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 1.0.5
>            Reporter: Vijay
>            Assignee: Vijay
>             Fix For: 1.2
>
>         Attachments: 0001-CASSANDRA-3555-v1.patch, 3555-bootstrap-with-down-node-test.txt, 3555-bootstrap-with-down-node.txt
>
>
> We might want to handle failures in bootstrapping:
> 1) When none of the Seeds are available to communicate then throw exception
> 2) When any one of the node which it is bootstrapping fails then try next in the list (and if the list is exhausted then throw exception).
> 3) Clean all the existing files in the data Dir before starting just in case we retry.
> 4) Currently when one node is down in the cluster the bootstrapping will fail, because the bootstrapping node doesnt understand which one is actually down.
> Also print the nt ring in the logs so we can troubleshoot later if it fails.
> Currently if any one of the above happens the node is skipping the bootstrap or hangs.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira