[distsql.go:1375] ["table reader fetch next chunk failed"] [conn=5246922264358639729] [error="context canceled"]

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

Original topic: [distsql.go:1375] [“table reader fetch next chunk failed”] [conn=5246922264358639729] [error=“context canceled”]

| username: cy6301567

There are a lot of such error logs appearing in the logs, what’s going on?

| username: ShawnYan | Original post link

Is this a post?

| username: ShawnYan | Original post link

First, check if there are any anomalies in the requests sent by the connection.

| username: redgame | Original post link

What are the front-end performance indicators?

| username: cy6301567 | Original post link

No impact on the business.

| username: jansu-dev | Original post link

Currently, there is too little information. Isn’t this error message incomplete?
Looking at v5, there is similar content, and it feels like it should have been fixed in v6.5.1.
If you want to check it yourself, you can refer to the idea in 5.0.0 upgrade to 5.0.1-pre, report “table reader fetch next chunk failed” · Issue #24148 · pingcap/tidb (github.com).
It seems that the log should later indicate something like “Transaction is corrupted by either missing data from default CF or some part of transaction are rollback.”

| username: TiDBer_vfJBUcxl | Original post link

It should be a failure to read the TiKV data transmitted over the network, possibly due to occasional network issues.

| username: TiDBer_vfJBUcxl | Original post link

You can check out this post: