Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

kvserver: check L0 sub-levels on allocation #13569

Open
cockroach-teamcity opened this issue Apr 11, 2022 · 0 comments
Open

kvserver: check L0 sub-levels on allocation #13569

cockroach-teamcity opened this issue Apr 11, 2022 · 0 comments

Comments

@cockroach-teamcity
Copy link
Member

cockroach-teamcity commented Apr 11, 2022

Exalate commented:

cockroachdb/cockroach#78608 --- Release note (ops change): introduce cluster settings kv.allocator.l0_sublevels_threshold and kv.allocator.L0_sublevels_threshold_enforce, which enable excluding stores as targets for allocation and rebalancing of replicas when they have high read amplification, indicated by the number of L0 sub-levels in level 0 of the store's LSM. When both kv.allocator.l0_sublevels_threshold and the cluster average is exceeded, the action corresponding to kv.allocator.l0_sublevels_threshold_enforce is taken. block_none will exclude no candidate stores, block_none_log will exclude no candidates but log an event, block_rebalance_to will exclude candidates stores from being targets of rebalance actions, block_all will exclude candidate stores from being targets of both allocation and rebalancing. Default kv.allocator.l0_sublevels_threshold is set to 20 and kv.allocator.l0_sublevels_threshold_enforce is set to block_none_log.

Jira Issue: DOC-3610

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants