[
https://issues.apache.org/jira/browse/CASSANDRA-4427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13420736#comment-13420736
]
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: https://github.com/jbellis/cassandra/tree/4427-5
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: https://issues.apache.org/jira/browse/CASSANDRA-4427
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
