cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (JIRA)" <j...@apache.org>
Subject [jira] [Reopened] (CASSANDRA-7069) Prevent operator mistakes due to simultaneous bootstrap
Date Mon, 15 Sep 2014 13:56:34 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-7069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Brandon Williams reopened CASSANDRA-7069:
-----------------------------------------

Hmm, it just occurred to me this prevents bootstrapping even after the two minute rule has
been followed.

> 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: 2.1.1, 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)

Mime
View raw message