spanconfigs: enable span config bounds by default #100120
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This change is |
We only clamp spanconfigs if the `spanconfig.bounds.enabled` cluster setting dictates as such. For 23.1, it's default off, but going forward we want it to be default on. Let's also make this cluster setting public. Epic: none Epic: CRDB-8035 Release note: None
arulajmani
force-pushed
the
scfg-bounds-default-on
branch
from
cf8da0b to
0d4c5bc
Compare
arulajmani
changed the title
knz
approved these changes
Mar 30, 2023
|
TFTR! bors r=knz |
|
Build succeeded: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We only clamp spanconfigs if the
spanconfig.bounds.enabledcluster setting dictates as such. For 23.1, it's default off, but going forward we want it to be default on. Let's also make this cluster setting public.Epic: none
Epic: CRDB-16706
Release note: None