-
Notifications
You must be signed in to change notification settings - Fork 1.2k
tikv: update auto compaction config #20708
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
Conversation
Signed-off-by: Yang Zhang <[email protected]>
Hi @v01dstar. Thanks for your PR. I'm waiting for a pingcap member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Signed-off-by: Yang Zhang <[email protected]>
/cc @Connor1996 |
/ok-to-test |
@v01dstar: Cannot trigger testing until a trusted user reviews the PR and leaves an In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
/cc @Oreoxmt |
/ok-to-test |
@v01dstar This PR removes the following TiKV configuration items:
If these configuration items are deprecated starting from v7.5.7 or v9.0.0, they should be marked as deprecated in the documentation rather than deleted. Typically, we deprecate a config in one release and remove it in a later release. If these items have already been removed from the codebase, it is appropriate to delete them from the configuration documentation. In that case, please also add corresponding release notes https://github.com/pingcap/docs-cn/pull/20705/files#diff-3ff8ef1f5dfa6d9aa8e12f68615eefd2c22f53ca43465a5efee9e2d066c597f3R16 to document this compatibility change. Additionally, consider adding a general note to help users understand the transition. For example:
|
Signed-off-by: Yang Zhang <[email protected]>
Done |
Co-authored-by: Grace Cai <[email protected]>
Co-authored-by: Grace Cai <[email protected]>
Co-authored-by: Grace Cai <[email protected]>
Co-authored-by: Grace Cai <[email protected]>
Co-authored-by: Grace Cai <[email protected]>
Co-authored-by: Grace Cai <[email protected]>
Co-authored-by: Grace Cai <[email protected]>
Co-authored-by: Grace Cai <[email protected]>
/approve |
/unhold |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Oreoxmt The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
In response to a cherrypick label: new pull request created to branch |
In response to a cherrypick label: new pull request created to branch |
In response to a cherrypick label: new pull request created to branch |
First-time contributors' checklist
What is changed, added or deleted? (Required)
Which TiDB version(s) do your changes apply to? (Required)
Tips for choosing the affected version(s):
By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.
For details, see tips for choosing the affected versions (in Chinese).
What is the related PR or file link(s)?
Do your changes match any of the following descriptions?