[ https://issues.apache.org/jira/browse/CASSANDRA-957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991058#comment-12991058 ]
Nick Bailey commented on CASSANDRA-957: --------------------------------------- What happens if I bring up a node with the same ip and bootstrap on but forget the replace option? It looks like it will try to bootstrap to an auto picked token. Am I reading that right? What happens if I accidentally give the wrong token with the replace option? If I accidentally give the token for a live node will it try to bootstrap to the same position? > convenience workflow for replacing dead node > -------------------------------------------- > > Key: CASSANDRA-957 > URL: https://issues.apache.org/jira/browse/CASSANDRA-957 > Project: Cassandra > Issue Type: Wish > Components: Core, Tools > Reporter: Jonathan Ellis > Assignee: Chris Goffinet > Fix For: 0.8 > > Attachments: > 0001-Support-bringing-back-a-node-to-the-cluster-that-exi.patch, > 0002-Do-not-include-local-node-when-computing-workMap.patch > > Original Estimate: 24h > Remaining Estimate: 24h > > Replacing a dead node with a new one is a common operation, but "nodetool > removetoken" followed by bootstrap is inefficient (re-replicating data first > to the remaining nodes, then to the new one) and manually bootstrapping to a > token "just less than" the old one's, followed by "nodetool removetoken" is > slightly painful and prone to manual errors. > First question: how would you expose this in our tool ecosystem? It needs to > be a startup-time option to the new node, so it can't be nodetool, and > messing with the config xml definitely takes the "convenience" out. A > one-off -DreplaceToken=XXY argument? -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira