[
https://issues.apache.org/jira/browse/CASSANDRA-15600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17049771#comment-17049771
]
Ekaterina Dimitrova commented on CASSANDRA-15600:
-------------------------------------------------
CI results attached. Two of the dtests turned out flakey on trunk, no new issue
introduced by this patch.
Respective issues were raised - CASSANDRA-15613 and CASSANDRA-15614
Patch:
[pull request|https://github.com/ekaterinadimitrova2/cassandra/pull/20]
[branch|https://github.com/ekaterinadimitrova2/cassandra/tree/CASSANDRA-15600]
> Algorithmic token allocation does not handle the racks = RF case well
> ---------------------------------------------------------------------
>
> Key: CASSANDRA-15600
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15600
> Project: Cassandra
> Issue Type: Bug
> Components: Feature/Virtual Nodes
> Reporter: Branimir Lambov
> Assignee: Ekaterina Dimitrova
> Priority: Normal
> Attachments: CASSANDRA-15600 unit.txt, CASSANDRA-15600-jvm.txt.zip,
> Screen Shot 2020-03-02 at 6.55.41 PM.png
>
>
> When the number of racks in a data centre is equal to the replication factor,
> the node allocation algorithm may calculate the target ownership incorrectly
> and allocate unsuitable tokens. This causes some inefficiency when the number
> of nodes in the DC is small, and significant problems if the number of nodes
> in each rack is different.
> In this case (racks count equal to replication factor) the load within each
> rack is effectively distributed independently. The allocation algorithm
> should reflect that, restricting the allocation space to the rack (instead of
> the DC) and using the RF=1 solution.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
