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

["Stefan Miklosovic (Jira)" <ji...@apache.org>]

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

Stefan Miklosovic commented on CASSANDRA-16203:
-----------------------------------------------

I would like to return to this ticket so we have a strategy which distributes replicas around racks in a more safer manner. 

It was a long time ago since we discussed this, I want to ask if something has changed since then when it comes to merging to trunk. I think we can pretty much ship it if we rebase and write tests for it?

I do not think "CEP" is necessary for this. I have never understood what that would be even about.

cc [~brandon.williams] [~paulo]

> 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: Sumanth Pasupuleti
>            Priority: Normal
>             Fix For: 4.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.20.10#820010)

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