You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Brandon Williams (JIRA)" <ji...@apache.org> on 2014/10/23 18:14:34 UTC

[jira] [Created] (CASSANDRA-8175) Extend existing endpoint check to also check when restarting normally

Brandon Williams created CASSANDRA-8175:
-------------------------------------------

             Summary: Extend existing endpoint check to also check when restarting normally
                 Key: CASSANDRA-8175
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8175
             Project: Cassandra
          Issue Type: Improvement
          Components: Core
            Reporter: Brandon Williams
            Assignee: Brandon Williams
             Fix For: 2.1.2


In CASSANDRA-5571 we added a check in shadow gossip to see if there was an existing node in gossip, but only if we bootstrap.  The scenario I want to prevent here is similar, but slightly different.  If someone restores a node to their development environment for whatever reason, they have a good chance of accidentally joining that node to the production cluster since it will know about the production cluster from the system table, and now this node will also have a higher generation than the existing one, causing a host id collision and knocking it out of the ring (except in its own view.)  Instead what I'd like to do is always do a shadow gossip round at startup, and check for conflicting host ids.  Obviously we'll want to bypass this for replacement.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)