-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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: add minimum cpu lb split threshold #98250
Conversation
It looks like your PR touches production code but doesn't add or edit any test code. Did you consider adding tests to your PR? 🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf. |
Previously, `kv.range_split.load_cpu_threshold` had no minimum setting value. It is undesirable to allow users to set this setting to low as excessive splitting may occur. `kv.range_split.load_cpu_threshold` now has a minimum setting value of `10ms`. Resolves: cockroachdb#98107 Release note (ops change): `kv.range_split.load_cpu_threshold` now has a minimum setting value of `10ms`.
9ee220b
to
903747d
Compare
It looks like your PR touches production code but doesn't add or edit any test code. Did you consider adding tests to your PR? Thank you for updating your pull request. My owl senses detect your PR is good for review. Please keep an eye out for any test failures in CI. 🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
As noted some of these parameters should not be TenantWritable, but you were going to create a separate PR for that.
TYFTR
Filed #98347 |
bors r=andrewbaptist |
Build succeeded: |
Previously,
kv.range_split.load_cpu_threshold
had no minimum setting value. It is undesirable to allow users to set this setting to low as excessive splitting may occur.kv.range_split.load_cpu_threshold
now has a minimum setting value of10ms
.See #96869 for additional context on the threshold.
Resolves: #98107
Release note (ops change):
kv.range_split.load_cpu_threshold
now has a minimum setting value of10ms
.