[
https://issues.apache.org/jira/browse/CASSANDRA-3041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Bailey updated CASSANDRA-3041:
-----------------------------------
Fix Version/s: (was: 1.0)
0.8.5
Marking this for the next 0.8.x version since the data duplication caused by
this bug is data that does actually belong on the nodes, so it can't be removed
by cleanup. It either has to be unduplicated with a major compaction or rely on
regular compaction.
> Move streams data to too many nodes.
> ------------------------------------
>
> Key: CASSANDRA-3041
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3041
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Affects Versions: 0.7.8, 0.8.4
> Reporter: Nick Bailey
> Fix For: 0.8.5
>
>
> When you decommission a node, it only streams data to the node that is just
> now gaining responsibility for the node's primary range.
> When you move a node it streams data to every node that is responsible for
> the node's primary range. This is way more than it needs to, and could be bad
> in multi-dc setups. We should absolutely use this bug as a chance/reason to
> better unify that code, since move should be doing the same thing decom does.
> This might be worth backporting to 0.8 as well.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
