[jira] [Commented] (CASSANDRA-21144) writePlacementsAllSettled can perform poorly in large clusters with many ongoing range movements

["Marcus Eriksson (Jira)" <ji...@apache.org>]

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

Marcus Eriksson commented on CASSANDRA-21144:
---------------------------------------------

looks good in general, two small comments on the pr

> writePlacementsAllSettled can perform poorly in large clusters with many ongoing range movements
> ------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-21144
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-21144
>             Project: Apache Cassandra
>          Issue Type: Bug
>          Components: Transactional Cluster Metadata
>            Reporter: Sam Tunnicliffe
>            Assignee: Sam Tunnicliffe
>            Priority: Normal
>             Fix For: 6.x
>
>         Attachments: ci_summary.html, result_details.tar.gz
>
>
> In a large cluster with multiple concurrent range movements in flight, calculating the final state of data placements after all movements are completed can be a CPU intensive operation. This is done solely to predict the future local write ranges so that DiskBoundaryManager can locate SSTables correctly on disk and reduce the relocation required to balance disks. 
> Calculating the outcome of every in-flight movement is overkill for this, as only the operations which affect the local node need to be considered.



--
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