cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-4427) Restarting a failed bootstrap instajoins the ring
Date Sun, 29 Jul 2012 17:29:34 GMT


Jonathan Ellis commented on CASSANDRA-4427:

bq. This doesn't quite work, because we're looking for the SCHEMA app state, which at startup
won't always exist

Added a quick fix for this case.  If the cluster is so new that there is no SCHEMA state,
then there's no actual schema info either.

bq. It's possible that you could have 3 seeds and all but one could be down, thus 2 gossip
rounds doesn't guarantee you'll have any appstates

Granted, but surely two rounds is a better measure than the zero we had before.  (Which apparently
worked most of the time...)  Remember, our goal is to avoid the full RING_DELAY sleep when
we don't need to bootstrap.
> Restarting a failed bootstrap instajoins the ring
> -------------------------------------------------
>                 Key: CASSANDRA-4427
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.0.0
>            Reporter: Brandon Williams
>            Assignee: Jonathan Ellis
>             Fix For: 1.1.3
>         Attachments: 4427-v2.txt, 4427-v3.txt, 4427.txt
> I think when we made auto_bootstrap = true the default, we broke the check for the bootstrap
flag, creating a dangerous situation.

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