[ https://issues.apache.org/jira/browse/CASSANDRA-7069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brandon Williams updated CASSANDRA-7069: ---------------------------------------- Attachment: 7069.txt Patch to refuse bootstrapping while other range movements are occurring and cassandra.consistent.rangemovement is true. > 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 > > Attachments: 7069.txt > > > 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.3.4#6332)