[
https://issues.apache.org/jira/browse/CASSANDRA-564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12786179#action_12786179
]
Jonathan Ellis commented on CASSANDRA-564:
------------------------------------------
I don't see where we do data transfers to move the right data to the node whose
range expands by the dead node being removed, or updating other replicas now
responsible for copies. We might need a new gossip state for that.
If that is done should we remove decommission as a redundant special case?
> Provide recoverability when a node dies and it is impossible to get the same
> IP.
> --------------------------------------------------------------------------------
>
> Key: CASSANDRA-564
> URL: https://issues.apache.org/jira/browse/CASSANDRA-564
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Anthony Molinaro
> Priority: Minor
> Fix For: 0.5
>
> Attachments: 564-2-fix-comment.patch, 564a.patch,
> 564b-use-tuple-state-left.patch
>
>
> From the descriptions on the mailing list, when a node dies permanently from
> hardware or other failure and you need to replace it, it must have the same
> IP. For people running in cloud environments, this is often times
> impossible. So it would be very useful if there was a way to replace a node
> with a new node without requiring the same IP.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
