cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Richard Low (Issue Comment Edited) (JIRA)" <>
Subject [jira] [Issue Comment Edited] (CASSANDRA-3555) Bootstrapping to handle more failure
Date Mon, 13 Feb 2012 11:22:59 GMT


Richard Low edited comment on CASSANDRA-3555 at 2/13/12 11:21 AM:

3555-bootstrap-with-down-node.txt contains a fix for 4, to stop a bootstrapping node choosing
an unavailable node.  3555-bootstrap-with-down-node-test.txt is required to make BootStrapperTest
pass with the patch.  Patches against trunk; same fix also works on 1.0 branch.
      was (Author: richardlow):
    A fix for 4, to stop a bootstrapping node choosing an unavailable node.
> Bootstrapping to handle more failure
> ------------------------------------
>                 Key: CASSANDRA-3555
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 1.0.5
>            Reporter: Vijay
>            Assignee: Vijay
>             Fix For: 1.2
>         Attachments: 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:!default.jspa
For more information on JIRA, see:


View raw message