[
https://issues.apache.org/jira/browse/CASSANDRA-16203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17400184#comment-17400184
]
Stefan Miklosovic edited comment on CASSANDRA-16203 at 8/17/21, 7:14 AM:
-------------------------------------------------------------------------
[~brandon.williams] do you think it makes sense to try to merge this now so it
would appear in 4.1? What release would you like to see this in? Any
preference? Or we trully wait for "5.0" whatever it might be ...
was (Author: stefan.miklosovic):
[~brandon.williams] do you think it makes sense to try to merge this now so it
would appear in 4.1? What release would you like to see this in? Any preference?
> 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: [email protected]
For additional commands, e-mail: [email protected]
