[
https://issues.apache.org/jira/browse/CASSANDRA-5128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Brown updated CASSANDRA-5128:
-----------------------------------
Attachment: 0001-CASSANDRA-5128-stream-hints-on-decommission.patch
Added code to SS.streamRanges() to check to see if there are any outstanding
hints to be played and if there are any available hosts to ship them to. If so,
then send all of the decommissioning node's hints over.
> 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
>
>
> 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
