TiDB logs continuously showing the same error: error="[server:8052]invalid sequence 105 != 1"

Translated
1

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

Original topic: tidb日志一直刷相同报错 error=“[server:8052]invalid sequence 105 != 1”

| username: xie123

【TiDB Usage Environment】Production Environment
【TiDB Version】V5.4.0
【Reproduction Path】Operations performed that led to the issue
【Encountered Issue: Issue Phenomenon and Impact】
No impact observed for now
tidb.log continuously reports errors
[ERROR] [terror.go:307] [“encountered error”] [error=“[server:8052]invalid sequence 105 != 1”] [stack=“github.com/pingcap/tidb/parser/terror.Log\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/parser/terror/terror.go:307\ngithub.com/pingcap/tidb/server.(*Server).onConn\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/server/server.go:516”]
【Resource Configuration】
【Attachments: Screenshots/Logs/Monitoring】

2
| username: Billmay表妹 | Original post link

What operation did you perform before encountering this error?

3
| username: xfworld | Original post link

It looks like there’s an issue with the sequence.

invalid sequence 105 != 1

If you don’t use sequences, you don’t need to pay much attention…
If you do use them, then quickly check the range.

4
| username: tidb菜鸟一只 | Original post link

It should not be related to the sequence, it should be an internal program error, an error on the MySQL protocol.

5
| username: xie123 | Original post link

Didn’t do anything.

6
| username: xie123 | Original post link

I didn’t see any sequence creation in the SQL.

7
| username: xie123 | Original post link

Any suggestions for troubleshooting directions?

8
| username: xfworld | Original post link

Keep observing.

9
| username: xie123 | Original post link

In the past month, there were only a few occasionally, but since yesterday until now, 230,000 entries have been processed…

10
| username: xfworld | Original post link

Generally, the encountered error will appear after analyze, and the given information is too little to make a judgment :rofl:

How about collecting the operation process before the problem occurred and the approximate changes in the logs before and after…

11
| username: xie123 | Original post link

Thanks, I roughly understand why. There’s a test program. I’ll look into the specific reason further.

12
| username: system | Original post link

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