cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "T Jake Luciani (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-7069) Prevent operator mistakes due to simultaneous bootstrap
Date Wed, 23 Apr 2014 01:17:14 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-7069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13977700#comment-13977700
] 

T Jake Luciani commented on CASSANDRA-7069:
-------------------------------------------

It will not throw an error but it defeats the purpose of the ticket.  I need to think about
it deeper, but if two nodes are bootstrapping and fall in the bounds of the original token
range then you would, in the end, not have a consistent bootstrap.

> 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)

Mime
View raw message