You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Rick Branson (JIRA)" <ji...@apache.org> on 2013/05/13 23:49:16 UTC

[jira] [Created] (CASSANDRA-5565) Peer entry drop from system table silently when bootstrapping a node with an existing IP.

Rick Branson created CASSANDRA-5565:
---------------------------------------

             Summary: Peer entry drop from system table silently when bootstrapping a node with an existing IP.
                 Key: CASSANDRA-5565
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5565
             Project: Cassandra
          Issue Type: Bug
          Components: Core
    Affects Versions: 1.2.4
            Reporter: Rick Branson


It looks like CASSANDRA-5167 introduced a bit of a regression. I needed to rebuild the data on a malfunctioning node by rebootstrapping it. I did this by cleaning the host and restarting Cassandra. My plan was to remove the old hostID once it had successfully bootstrapped. 

No errors were encountered, but the old host ID of the node before the wipe was completely dropped from the peers table because they had the same IP address, and therefore the data ranges were moved around. This resulted in a large number of CL.ONE reads coming back empty.

There might be a better approach to this rebootstrap process, but it seems like it's dangerous to just drop the peer from the table, especially without any kind of log message.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira