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 Mon, 23 Jul 2012 16:07:34 GMT


Jonathan Ellis commented on CASSANDRA-4427:

bq. there is still one behavior that the patch changes, that is it will always boobstrap non
seeds node

You're right.  Okay, take five:

4 patches here on top of Brandon's work.  The main ones are the 1st and 4th.  In the first,
I remove the seed special case since it's a subset of the empty schema case.  (Unless you're
Doing It Wrong and adding seed nodes directly to an active cluster, which always surprises
people when it burns them.  So I say good riddance.)

The first also adds a 2-gossip-round sleep so that (always assuming seeds are set correctly)
we eliminate the risk of thinking schema is empty incorrectly due to a race w/ gossip.  The
fourth patch follows this up by making the schema check based on other peers' schema uuids
instead of local data.  Which is unlikely to be a problem today, but is is still a race-y
approach and the correct alternative was straightforward.
> 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.0.11, 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