8-resource_exhausted sent message larger than max

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

Original topic: 8-resource_exhausted sent message larger than max

| username: ablewang_xiaobo

【TiDB Usage Environment】Production Environment
【TiDB Version】v5.2.2
【Encountered Problem】
【Reproduction Path】What operations were performed that caused the problem
【Problem Phenomenon and Impact】

| username: ablewang_xiaobo | Original post link

The image you provided is not visible. Please provide the text you need translated.

| username: 长安是只喵 | Original post link

What operation were you performing when this error message appeared?
There are similar posts in the community:

| username: ablewang_xiaobo | Original post link

This was extracted from the dashboard logs. It’s an error on TiKV, and there is no binlog in this environment.

| username: ablewang_xiaobo | Original post link

| username: 长安是只喵 | Original post link

Is the client reporting “scheduler is busy”?
I don’t know if this is the same as yours.

| username: ablewang_xiaobo | Original post link

There is no such error.

| username: zzzzzz | Original post link

Could you please check if this is the scenario?

| username: system | Original post link

This topic will be automatically closed 60 days after the last reply. No new replies are allowed.