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 2013/08/21 19:12:55 UTC

[jira] [Created] (CASSANDRA-5916) gossip and tokenMetadata get hostId out of sync on failed replace_node

Brandon Williams created CASSANDRA-5916:
-------------------------------------------

             Summary: gossip and tokenMetadata get hostId out of sync on failed replace_node
                 Key: CASSANDRA-5916
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5916
             Project: Cassandra
          Issue Type: Bug
            Reporter: Brandon Williams
            Assignee: Brandon Williams
             Fix For: 1.2.9


If you try to replace_node an existing, live hostId, it will error out.  However if you're using an existing IP to do this (as in, you chose the wrong uuid to replace on accident) then the newly generated hostId wipes out the old one in TMD, and when you do try to replace it replace_node will complain it does not exist.  Examination of gossipinfo still shows the old hostId, however now you can't replace it either.

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