tikv / titan: Add note for disabling titan #20304
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. |
ti-chi-bot
bot
added
needs-ok-to-test
| @@ -170,7 +170,10 @@ level-merge = false | |||
|
|
|||
| 3. 等待数据整理结束，通过 **TiKV-Details**/**Titan - kv** 监控面板确认 **Blob file count** 指标降为 0。 | |||
|
|
|||
There was a problem hiding this comment.
对于 v8.5 之前分支的文档，为了避免用户执行这个步骤导致 TiKV crash，我们是直接删掉这个步骤 4 就可以了吗
|
@glorv: adding LGTM is restricted to approvers and reviewers in OWNERS files. 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. |
qiancai
added
needs-cherry-pick-release-8.5
[LGTM Timeline notifier]Timeline:
|
Co-authored-by: Grace Cai <[email protected]>
qiancai
added
the
needs-cherry-pick-release-8.1
|
/ok-to-test |
ti-chi-bot
bot
added
ok-to-test
qiancai
added
translation/done
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: qiancai 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 |
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?