tikv: add the user's guide of stale read and safe ts #15365
Conversation
Signed-off-by: Aolin <aolin.zhang@pingcap.com>
ti-chi-bot
bot
added
missing-translation-status
Oreoxmt
added
translation/from-docs
ti-chi-bot
bot
removed
the
missing-translation-status
| - Resolved-TS worker CPU：resolved-ts worker 线程的 CPU 使用率 | ||
| - Advance-TS worker CPU：advance-ts worker 线程的 CPU 使用率 | ||
| - Scan lock worker CPU：scan lock worker 线程的 CPU 使用率 | ||
| - Max gap of resolved-ts：在当前 TiKV 中，所有活跃 Region 的 resolved-ts 与当前时间的最大差值 |
There was a problem hiding this comment.
截图上的名称是 Max Resolved TS gap
| - Max gap of resolved-ts：在当前 TiKV 中，所有活跃 Region 的 resolved-ts 与当前时间的最大差值 | |
| - Max Resolved TS gap：在当前 TiKV 中，所有活跃 Region 的 resolved-ts 与当前时间的最大差值 |
There was a problem hiding this comment.
@ekexium PTAL and update the English document if necessary.
There was a problem hiding this comment.
In older version it's "Max Resolved TS gap". It's been renamed to "Max gap of resolved-ts". The pic is captured from an older version.
There was a problem hiding this comment.
Should we update this pic? media/stale-read/example-ts-gap.png
There was a problem hiding this comment.
Not necessary. We can comment the rename here
There was a problem hiding this comment.
Co-authored-by: xixirangrang <hfxsd@hotmail.com>
Co-authored-by: ekexium <eke@fastmail.com>
|
@ekexium: 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/test-infra repository. |
[LGTM Timeline notifier]Timeline:
|
|
/approve |
|
[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 |
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
|
In response to a cherrypick label: new pull request created to branch |
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
|
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)
get-region-read-progressWhich 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.
What is the related PR or file link(s)?
Do your changes match any of the following descriptions?