[
https://issues.apache.org/jira/browse/CASSANDRA-4427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13417016#comment-13417016
]
Brandon Williams commented on CASSANDRA-4427:
---------------------------------------------
bq. The fact is that recording that bootstrap is in progress (along with the
system table check) would allow to fix the instajoin while keeping the current
behavior unchanged otherwise, and I do feel that recording the info is not a
bad idea in itself, so that would have my preference.
I tend to agree that having an explicit, persisted flag feels a lot less
fragile than the current logic, and being able to indicate a failure to the
user seems like a good improvement.
> 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
