[
https://issues.apache.org/jira/browse/CASSANDRA-5128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13556452#comment-13556452
]
Jason Brown commented on CASSANDRA-5128:
----------------------------------------
Crap, yeah, I see that now. Maybe we should move the hints streaming code out
of streamRanges() and up into unbootstrap() to avoid the overlap with move. WRT
a separate streaming session, I though it already was separate as
StreamOut.transferRanges() creates a new StreamOutSession. I could be
misunderstanding the question, though.
> Stream hints on decommission
> ----------------------------
>
> Key: CASSANDRA-5128
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5128
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Affects Versions: 1.2.1
> Reporter: Jason Brown
> Assignee: Jason Brown
> Labels: decommission, hints
> Attachments: 0001-CASSANDRA-5128-stream-hints-on-decommission.patch,
> 5128-v2.txt
>
>
> Looks like decommissioning a node (nodetool decommission) will stream all the
> non-system table data out to it's appropriate peers
> (StorageService.unbootstrap()), but hints will disappear with the node. Let's
> send those hints to another peer (preferably in the same rack, and hopefully
> at least the same datacenter) them to be replayed.
> The use case here is auto-scaling vnode clusters in ec2. When auto-scaling
> down, I'd want to call decommission on the node to leave the ring (and be
> terminated), and still have all of it's artifacts (data and hints) survive.
--
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
