cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-3041) Move streams data to too many nodes.
Date Tue, 13 Sep 2011 19:21:09 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-3041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13103917#comment-13103917
] 

Jonathan Ellis commented on CASSANDRA-3041:
-------------------------------------------

>From IRC:

{quote}
nickmbailey: new patch looks fine, the news.txt update should say move/decomm though
{quote}

> 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

        

Mime
View raw message