[
https://issues.apache.org/jira/browse/CASSANDRA-16203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Miklosovic updated CASSANDRA-16203:
------------------------------------------
Status: Patch Available (was: In Progress)
https://github.com/apache/cassandra/pull/2191
I have tested this via "NetworkTopologyStrategy" test which I made parametrized
where both NTS and this strategy is tested.
There is one test which is not running which tests "the old algorithm" NTS is
compatible with when that test was written (because NTS was itself implementing
some improvements) but this strategy is not compatible with that any more as it
places replicas differently. Apart from that, all tests are compatible with NTS
way of doing things.
> 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: Stefan Miklosovic
> 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: [email protected]
For additional commands, e-mail: [email protected]
