[ https://issues.apache.org/jira/browse/CASSANDRA-1216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12899993#action_12899993 ]
Nick Bailey commented on CASSANDRA-1216: ---------------------------------------- Yeah I wasn't really understanding that streaming/messaging code at all. The current StreamOut implementation has a callback concept however. I think this should be moved into the StreamContext object and then both StreamOut and StreamIn can perform callbacks on actual stream completion. > removetoken drops node from ring before re-replicating its data is finished > --------------------------------------------------------------------------- > > Key: CASSANDRA-1216 > URL: https://issues.apache.org/jira/browse/CASSANDRA-1216 > Project: Cassandra > Issue Type: Bug > Components: Core > Reporter: Jonathan Ellis > Assignee: Nick Bailey > Fix For: 0.7 beta 2 > > Attachments: > 0001-Modify-removeToken-to-be-similar-to-decommission.patch, > 0002-Fixes-to-old-tests.patch, > 0003-Additional-unit-tests-for-removeToken.patch > > > this means that if something goes wrong during the re-replication (e.g. a > source node is restarted) there is (a) no indication that anything has gone > wrong and (b) no way to restart the process (other than the Big Hammer of > running repair) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.