Skip to content

docs: sync Resolved TS row/panel names with TiKV dashboard #23922

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.

Sign up for GitHub

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

Merged
ti-chi-bot merged 5 commits into from
Sep 22, 2026
Merged

docs: sync Resolved TS row/panel names with TiKV dashboard #23922

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
f576afb
Initial plan
Copilot Sep 21, 2026
fe12309
docs: sync resolved ts panel names with TiKV dashboard
Copilot Sep 21, 2026
6eb3579
docs: fix tikv-control panel reference
Copilot Sep 22, 2026
44e0932
Add back a file
lilin90 Sep 22, 2026
1e2fc0a
Update troubleshoot-stale-read.md
lilin90 Sep 22, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 8 additions & 8 deletions grafana-tikv-dashboard.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -452,17 +452,17 @@ The following metrics are related to [TiKV MVCC In-Memory Engine](/tikv-in-memor
- Total pessimistic locks memory size: The memory size occupied by the in-memory pessimistic locks
- In-memory pessimistic locking result: The result of only saving pessimistic locks to memory. `full` means the number of times that the pessimistic lock is not saved to memory because the memory limit is exceeded.

### Resolved-TS
### Resolved TS

- Resolved-TS worker CPU: The CPU utilization of the resolved-ts worker threads
- Advance-TS worker CPU: The CPU utilization of the advance-ts worker threads
- Scan lock worker CPU: The CPU utilization of the scan lock worker threads
- Resolved TS Worker CPU: The CPU utilization of the resolved-ts worker threads
- Advance ts Worker CPU: The CPU utilization of the advance-ts worker threads
- Scan lock Worker CPU: The CPU utilization of the scan lock worker threads
- Max gap of resolved-ts: The maximum time difference between the resolved-ts of all active Regions in this TiKV and the current time
- Max gap of safe-ts: The maximum time difference between the safe-ts of all active Regions in this TiKV and the current time
- Max gap of follower safe-ts: The maximum time difference between the minimum non-zero safe-ts of followers in this TiKV and the current time
- Min Resolved TS Region: The ID of the Region whose resolved-ts is the minimal
- Min Safe TS Region: The ID of the Region whose safe-ts is the minimal
- Check Leader Duration: The distribution of time spent on processing leader requests. The duration is from sending requests to receiving responses in leader
- Max gap of resolved-ts in Region leaders: The maximum time difference between the resolved-ts of all active Regions in this TiKV and the current time, only for Region leaders
- Min Safe TS Follower Region: The ID of the follower Region whose safe-ts is the minimal
Comment thread
lilin90 marked this conversation as resolved.
- Check leader duration: The distribution of time spent on processing leader requests. The duration is from sending requests to receiving responses in leader
Comment thread
lilin90 marked this conversation as resolved.
- Max gap of resolved-ts in region leaders: The maximum time difference between the resolved-ts of all active Regions in this TiKV and the current time, only for Region leaders
- Min Leader Resolved TS Region: The ID of the Region whose resolved-ts is the minimal, only for Region leaders
- Lock heap size: The size of the heap that tracks locks in the resolved-ts module

Expand Down
2 changes: 1 addition & 1 deletion tikv-control.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -648,7 +648,7 @@ From the output above, you can see that the information of the damaged SST file

### Get the state of a Region's `RegionReadProgress`

Starting from v6.5.4 and v7.3.0, TiKV introduces the `get-region-read-progress` subcommand to get up-to-date details of the resolver and `RegionReadProgress`. You need to specify a Region ID and a TiKV, which can be obtained from Grafana (`Min Resolved TS Region` and `Min Safe TS Region`) or `DataIsNotReady` logs.
Starting from v6.5.4 and v7.3.0, TiKV introduces the `get-region-read-progress` subcommand to get up-to-date details of the resolver and `RegionReadProgress`. You need to specify a Region ID and a TiKV, which can be obtained from Grafana (`Min Resolved TS Region` and `Min Safe TS Follower Region`) or `DataIsNotReady` logs.

- `--log` (optional): If specified, TiKV logs the smallest `start_ts` of locks in the Region's resolver in this TiKV at `INFO` level. This option helps you identify locks that might block resolved-ts in advance.

Expand Down
2 changes: 1 addition & 1 deletion troubleshoot-stale-read.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -160,7 +160,7 @@ To address this issue:

### Address CheckLeader issues

To address CheckLeader issues, you can check the network and the **Check Leader Duration** metric in [**TiKV-Details** > **Resolved-TS** dashboard](/grafana-tikv-dashboard.md#resolved-ts).
To address CheckLeader issues, you can check the network and the **Check leader duration** metric in [**TiKV-Details** > **Resolved TS** dashboard](/grafana-tikv-dashboard.md#resolved-ts).

## Example

Expand Down
Loading