You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2014/05/02 23:26:17 UTC

[jira] [Commented] (CASSANDRA-6551) Rack-aware batchlog replication

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

Jonathan Ellis commented on CASSANDRA-6551:
-------------------------------------------

v2 attached that does some cleanup (leave return type Collection so we don't need to copy into Lists unnecessarily) and restores randomness of endpoints per rack.

The randomness breaks the hardcoded tests so I'm going to throw it back to you to figure out what to do about that. :)

> Rack-aware batchlog replication
> -------------------------------
>
>                 Key: CASSANDRA-6551
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6551
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Rick Branson
>            Assignee: Mikhail Stepura
>            Priority: Minor
>             Fix For: 2.1 rc1
>
>         Attachments: 6551-v2.txt, cassandra-2.0-6551-2.patch
>
>
> Right now the batchlog replication code just randomly picks 2 other nodes in the same DC, regardless of rack. Ideally we'd pick 2 replicas in other racks to achieve higher fault tolerance.



--
This message was sent by Atlassian JIRA
(v6.2#6252)