[
https://issues.apache.org/jira/browse/CASSANDRA-17868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17603709#comment-17603709
]
Josh McKenzie commented on CASSANDRA-17868:
-------------------------------------------
||Item|Link||
|PR|[link|https://github.com/apache/cassandra/pull/1855]|
|JDK8
CI|[link|https://app.circleci.com/pipelines/github/josh-mckenzie/cassandra/295/workflows/c33ed2b0-5063-4707-ba65-075b38dd9361]|
|JDK11
CI|[link|https://app.circleci.com/pipelines/github/josh-mckenzie/cassandra/295/workflows/274b3677-f709-4e07-be40-a6ad4bc97f59]|
> Allow disabling hotness persistence, or tuning of rate limiter
> --------------------------------------------------------------
>
> Key: CASSANDRA-17868
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17868
> Project: Cassandra
> Issue Type: Improvement
> Components: Feature/Rate Limiting
> Reporter: Josh McKenzie
> Assignee: Josh McKenzie
> Priority: Normal
> Fix For: 4.x
>
>
> The persisting of the sstables hotness when there are 10s of thousands of
> sstables can have issues keeping up, and the rate limiter is hard coded.
> Another option may be nice to just completely disable the feature.
> When sstables super backed up (from repairs) the hotness tracking tends to
> cause the STCS in L0 to make poor decisions, always grabbing the large
> sstables and skipping the tiny sstables that would benefit more.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
