[
https://issues.apache.org/jira/browse/CASSANDRA-7069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13977715#comment-13977715
]
T Jake Luciani commented on CASSANDRA-7069:
-------------------------------------------
Right, I agree. What I'm saying it we may need to error any simultaneous
bootstraps, they would need to happen fully one at a time.
Honestly I don't understand how the "shadow" round works well enough to know if
two bootstraps placed N minutes apart will end up with consistency issues ala
2434 but I suspect it would be an issue.
> Prevent operator mistakes due to simultaneous bootstrap
> -------------------------------------------------------
>
> Key: CASSANDRA-7069
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7069
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: Brandon Williams
> Assignee: Brandon Williams
> Priority: Minor
> Fix For: 3.0
>
>
> Cassandra has always had the '2 minute rule' between beginning topology
> changes to ensure the range announcement is known to all nodes before the
> next one begins. Trying to bootstrap a bunch of nodes simultaneously is a
> common mistake and seems to be on the rise as of late.
> We can prevent users from shooting themselves in the foot this way by looking
> for other joining nodes in the shadow round, then comparing their generation
> against our own and if there isn't a large enough difference, bail out or
> sleep until it is large enough.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
