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

Sam Tunnicliffe edited comment on CASSANDRA-21456 at 6/17/26 5:03 PM:
----------------------------------------------------------------------

I've combined the patches for CASSANDRA-21454, CASSANDRA-21455 & 
CASSANDRA-21456 and am running CI against that 
[branch|https://github.com/beobal/cassandra/tree/21454_21455_21456].


was (Author: beobal):
I've combined the patches for CASSANDRA-21454, CASSANDRA-21455 & 
CASSANDRA-21456 and am running CI against that branch.

> Add policy for selecting CMS host when submitting commit request
> ----------------------------------------------------------------
>
>                 Key: CASSANDRA-21456
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-21456
>             Project: Apache Cassandra
>          Issue Type: Improvement
>          Components: Transactional Cluster Metadata
>            Reporter: Sam Tunnicliffe
>            Assignee: Jon Meredith
>            Priority: Normal
>             Fix For: 6.x
>
>         Attachments: ci_summary.html, result_details.tar.gz
>
>
> While running experiments on clusters with 1000+ nodes and multiple 
> concurrent range movements, we found a lot of paxos contention on  the CMS 
> instances. Which CMS member an instance submits requests to is currently 
> selected at random, causing the contention and  ultimately leading to write 
> timeout failures.
> One option is the addition of a policy setting to choose between random and 
> deterministic CMS member selection and whether to prefer the local DC for 
> changes or select globally.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to