GC Work Error Log

Translated
1

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

Original topic: GC work错误日志

| username: TiDBer_i3pbMJ65

[TiDB Usage Environment] Production Environment / Testing / PoC
[TiDB Version] 7.5.1
[Reproduction Path] What operations were performed when the issue occurred: Normal CRUD operations, used quite a few select for update statements. The cluster load is very low.
[Encountered Issue: Issue Phenomenon and Impact]
TiDB printed a lot of the following error logs

image
image1380×702 486 KB

[Resource Configuration] Go to TiDB Dashboard - Cluster Info - Hosts and take a screenshot of this page
[Attachments: Screenshots/Logs/Monitoring]

2
| username: zhh_912 | Original post link

You can ignore the warning logs and only look at the errors. It is likely a transaction write conflict.

3
| username: TiDBer_i3pbMJ65 | Original post link

Is this conflict caused by the user’s write operation or by TiDB’s background task write operation? It looks a bit like it was printed by gcwork.

4
| username: 鱼跃龙门 | Original post link

This is a conflict caused by two transactions writing concurrently.

5
| username: 友利奈绪 | Original post link

The warning should not affect actual storage, right?

6
| username: TiDBer_H5NdJb5Q | Original post link

Mark, how does write conflict affect GC?

7
| username: 小于同学 | Original post link

Does it affect normal use?

8
| username: 濱崎悟空 | Original post link

Concurrency conflict?

9
| username: ziptoam | Original post link

It might be caused by transaction concurrency conflicts.

10
| username: Hacker_zuGnSsfP | Original post link

Just focus on the error logs.