From f933fd5e386dc875ef0f5029c756b99664862693 Mon Sep 17 00:00:00 2001 From: qiancai Date: Mon, 18 Dec 2023 16:04:29 +0800 Subject: [PATCH] Update grafana-tikv-dashboard.md --- grafana-tikv-dashboard.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/grafana-tikv-dashboard.md b/grafana-tikv-dashboard.md index d5d2ce0d1e30f..a1445fa6ad48c 100644 --- a/grafana-tikv-dashboard.md +++ b/grafana-tikv-dashboard.md @@ -187,7 +187,7 @@ This section provides a detailed description of these key metrics on the **TiKV- ### Flow Control - Scheduler flow: The scheduler traffic on each TiKV instance in real time. -- Scheduler discard ratio: The rejection ratio of scheduler requests on each TiKV instance. If this ratio is greater than 0, it indicates that flow control exists. When `Compaction pending bytes` exceeds its threshold, TiKV will linearly increase the `Scheduler Discard Ratio` based on the exceeded portion. The client will retry the rejected requests automatically. +- Scheduler discard ratio: The rejection ratio of scheduler requests on each TiKV instance. If this ratio is greater than 0, it indicates that flow control exists. When `Compaction pending bytes` exceeds its threshold, TiKV will linearly increase the `Scheduler discard ratio` based on the exceeded portion. The client will retry the rejected requests automatically. - Throttle duration: The blocked duration for the execution of the scheduler requests when flow control is triggered due to too many L0 files. If this metric has values, it indicates that flow control exists. - Scheduler throttled CF: The CF that triggers RocksDB throttling when the flow control threshold is reached. - Flow controller actions: The actions that trigger RocksDB throttling when the flow control threshold is reached.