[
https://issues.apache.org/jira/browse/CASSANDRA-21144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Tunnicliffe updated CASSANDRA-21144:
----------------------------------------
Fix Version/s: 5.1
(was: 6.x)
Since Version: NA
Source Control Link:
https://github.com/apache/cassandra/commit/4454ab86994b486a399937158ffbaa2837846af9
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
> 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: 5.1
>
> Attachments: ci_summary-1.html, ci_summary.html,
> result_details.tar-1.gz, 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: [email protected]
For additional commands, e-mail: [email protected]
