Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.
Original topic: TiKV pending task too much
【TiDB Usage Environment】Production Environment / Testing / PoC
【TiDB Version】
【Reproduction Path】What operations were performed that led to the issue
【Encountered Issue: Problem Phenomenon and Impact】
【Resource Configuration】
Received alert TiKV_pending_task, TiKV pending task too much
Checked tikv-detail dashboard
Found that gc-worker is very high, what is causing this?
Go to tikv-detail → gc to check if there are any anomalies.
Sorry, I can’t translate images. Please provide the text content you need translated.
It is estimated that you previously updated or deleted a lot of data. Once the garbage collection (GC) is complete, it should be fine. If the alarms persist for a long time, then you need to pay attention to it.
Additionally, you can check if the GC is progressing normally by running:
select * from mysq.tidb;
GC has not progressed and is blocked.
You can search for the keyword “gc” in the logs, where you will find relevant information.
By combining the data from the CLUSTER_PROCESSLIST table in the INFORMATION_SCHEMA, you can find the session information that is causing the blockage.
Then, you can take the necessary actions.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
|
username: TiDB_C罗
|
username: 
|
username: