You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Sumanth Pasupuleti (Jira)" <ji...@apache.org> on 2021/08/11 14:58:00 UTC

[jira] [Commented] (CASSANDRA-16203) Rack Aware Topology Strategy

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

Sumanth Pasupuleti commented on CASSANDRA-16203:
------------------------------------------------

[~cam1982] I think this may qualify for getting a CEP done. [~paulo] thoughts?

> Rack Aware Topology Strategy
> ----------------------------
>
>                 Key: CASSANDRA-16203
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-16203
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Cluster/Membership
>            Reporter: Cameron Zemek
>            Assignee: Cameron Zemek
>            Priority: Normal
>             Fix For: 5.x
>
>         Attachments: rackaware.patch
>
>
> If replication factor > racks then NetworkTopologyStrategy assigns the extras in ring order. This means losing a rack can result in the loss of quorum. I have implemented a similar topology strategy that evenly distributes replicas across racks.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org