Alert: TiKV pending task too much type: resolved-ts

This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: 报警TiKV pending task too much type: resolved-ts

| username: chenhanneu

[TiDB Usage Environment] Production Environment / Testing / POC
[TiDB Version]
[Reproduction Path] What operations were performed when the issue occurred
[Encountered Issue: Issue Phenomenon and Impact]
[Resource Configuration] Go to TiDB Dashboard - Cluster Info - Hosts and take a screenshot of this page
[Attachments: Screenshots / Logs / Monitoring]

Warning Log:
[WARNING] TiKV pending task too much
Cluster: xxxxx
Content: type: resolved-ts, instance: xxxxx, values: 3374

There are a large number of updates during the time period. Do we need to handle this warning?

| username: xfworld | Original post link

Is it caused by extremely large batch processing? If so, then such a warning is normal.
Refer here:

It is recommended that the business unit follow the suggestions in the documentation to make some optimizations to avoid long transaction commit times or transactions existing for too long before committing.

| username: miya | Original post link

If there are large transactions, it is recommended to break them down into smaller transactions for execution.

| username: zhang_2023 | Original post link

Try to avoid large transactions and long transactions as much as possible.

| username: dba远航 | Original post link

Avoid large transactions and long transactions.

| username: TiDBer_QYr0vohO | Original post link

Avoid large transactions.

| username: zhaokede | Original post link

Long transactions, try to break them down in the business logic.

| username: system | Original post link

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.