update(tidb-troubleshooting-map): add flow control instruction on top…
First-time contributors' checklist
- [x] I've signed Contributor License Agreement that's required for repo owners to accept my contribution.
What is changed, added or deleted? (Required)
update tide-trouble-shooting-map.md, update the tikv server is busy part
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.
- [x] master (the latest development version)
- [x] v7.6 (TiDB 7.6 versions)
- [x] v7.5 (TiDB 7.5 versions)
- [x] v7.4 (TiDB 7.4 versions)
- [x] v7.3 (TiDB 7.3 versions)
- [x] v7.1 (TiDB 7.1 versions)
- [x] v6.5 (TiDB 6.5 versions)
- [x] v6.1 (TiDB 6.1 versions)
- [x] v5.4 (TiDB 5.4 versions)
- [x] v5.3 (TiDB 5.3 versions)
- [x] v5.2 (TiDB 5.2 versions)
- [ ] v5.1 (TiDB 5.1 versions)
- [ ] v5.0 (TiDB 5.0 versions)
What is the related PR or file link(s)?
- This PR is translated from: https://github.com/pingcap/docs-cn/pull/16193
- Other reference link(s):
related Change Request https://github.com/pingcap/docs-cn/issues/8135 I'm participating the 2024-tidb-doc-dash https://github.com/orgs/pingcap/projects/51/views/3
Do your changes match any of the following descriptions?
- [ ] Delete files
- [ ] Change aliases
- [ ] Need modification after applied to another branch
- [ ] Might cause conflicts after applied to another branch
Welcome @hzc989!
It looks like this is your first PR to pingcap/docs 🎉.
I'm the bot to help you request reviewers, add labels and more, See available commands.
We want to make sure your contribution gets all the attention it needs!
Thank you, and welcome to pingcap/docs. :smiley:
Hi @hzc989, I'm sorry to let you know that, according to the confirmation from @Connor1996 (a developer of TiKV), the issue #8135 is invalid and does not necessitate any documentation updates. Nonetheless, you'll still get the points for creating this PR in the Docs Dash 2024 event, and I sincerely appreciate your effort on resolving this issue.
If it is acceptable to you, could you please close this PR? Thanks.
Hi @hzc989, I'm sorry to let you know that, according to the confirmation from @Connor1996 (a developer of TiKV), the issue #8135 is invalid and does not necessitate any documentation updates. Nonetheless, you'll still get the points for creating this PR in the Docs Dash 2024 event, and I sincerely appreciate your effort on resolving this issue.
If it is acceptable to you, could you please close this PR? Thanks.
Do not bother to close it, the description still needs to be updated for flow control.
Hi @hzc989, would you please update the English PR according to the latest changes in https://github.com/pingcap/docs-cn/pull/16193? Thanks.
Hi @qiancai , updated , plz review.
[LGTM Timeline notifier]
Timeline:
/retest
/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
- ~~OWNERS~~ [qiancai]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
In response to a cherrypick label: new pull request created to branch release-8.0: #17486.
In response to a cherrypick label: new pull request created to branch release-7.5: #17487.
In response to a cherrypick label: new pull request created to branch release-7.6: #17488.