cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vijay (Commented) (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3555) Bootstrapping to handle more failure
Date Thu, 08 Mar 2012 22:35:58 GMT


Vijay commented on CASSANDRA-3555:

Hi Brandon, Sorry that was a typo (When this patch was created the build was failing because
of it logger_ was renamed to logger). I will fix it if everything else is ok :)
> 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: 0001-CASSANDRA-3555-v1.patch, 3555-bootstrap-with-down-node-test.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