[
https://issues.apache.org/jira/browse/CASSANDRA-3041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13104560#comment-13104560
]
Hudson commented on CASSANDRA-3041:
-----------------------------------
Integrated in Cassandra-0.8 #327 (See
[https://builds.apache.org/job/Cassandra-0.8/327/])
Avoid streaming data to nodes that already have it, on move as well as
decommission
patch by Nick Bailey and jbellis for CASSANDRA-3041
jbellis :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1170306
Files :
* /cassandra/branches/cassandra-0.8/CHANGES.txt
*
/cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/service/StorageService.java
> 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.8.4
> Reporter: Nick Bailey
> Assignee: Nick Bailey
> Priority: Minor
> Fix For: 0.8.6
>
> Attachments:
> 0001-Don-t-stream-to-replicas-that-already-have-the-data.patch, 3041-v2.txt
>
>
> 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
