conf: rewrite unified pool related configurations #7946
Merged
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.
What problem does this PR solve?
Problem Summary:
When TiKV starts, it prints out the configuration in the log. Currently, if
use-unified-pool
is not set,null
will be outputted. This behavior may be confusing to users and the users can fail to know the default setting TiKV uses.What is changed and how it works?
What's Changed:
Instead of silently using default settings in TiKV, this PR rewrites
use-unified-pool
with the default setting. Now TiKV prints out the real setting ofuse-unifed-pool
in the start log.Related changes
Check List
Tests
Now, even if
use-unified-pool
is not set, the real setting will be printed out like this: (previously readpool.*.use-unified.pool = null)Release note
Prints out the factual
use-unified-pool
configuration in the startup log.