Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tidb can't start for the error of invalid ddl job type: none when upgrade master #39659

Closed
lilinghai opened this issue Dec 6, 2022 · 5 comments
Assignees
Labels
severity/critical sig/sql-infra SIG: SQL Infra type/bug The issue is confirmed as a bug.

Comments

@lilinghai
Copy link
Contributor

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

deploy a tidb cluster with more than 1 tidb
upgrade from v6.1.0 to master

[2022/12/06 13:49:28.842 +08:00] [FATAL] [bootstrap.go:1096] ["doReentrantDDL error"] [error="[ddl:8204]invalid ddl job type: none"] [stack="[github.com/pingcap/tidb/session.doReentrantDDL\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/session/bootstrap.go:1096\ngit.luolix.top/pingcap/tidb/session.upgradeToVer107\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/session/bootstrap.go:2181\ngit.luolix.top/pingcap/tidb/session.upgrade\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/session/bootstrap.go:941\ngit.luolix.top/pingcap/tidb/session.runInBootstrapSession\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/session/session.go:3114\ngit.luolix.top/pingcap/tidb/session.BootstrapSession\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/session/session.go:2966\nmain.createStoreAndDomain\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/tidb-server/main.go:312\nmain.main\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/tidb-server/main.go:213\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:250](http://github.com/pingcap/tidb/session.doReentrantDDL/n/t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/session/bootstrap.go:1096/ngit.luolix.top/pingcap/tidb/session.upgradeToVer107/n/t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/session/bootstrap.go:2181/ngit.luolix.top/pingcap/tidb/session.upgrade/n/t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/session/bootstrap.go:941/ngit.luolix.top/pingcap/tidb/session.runInBootstrapSession/n/t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/session/session.go:3114/ngit.luolix.top/pingcap/tidb/session.BootstrapSession/n/t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/session/session.go:2966/nmain.createStoreAndDomain/n/t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/tidb-server/main.go:312/nmain.main/n/t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/tidb-server/main.go:213/nruntime.main/n/t/usr/local/go/src/runtime/proc.go:250)"]

2. What did you expect to see? (Required)

3. What did you see instead (Required)

4. What is your TiDB version? (Required)

master

@lilinghai lilinghai added the type/bug The issue is confirmed as a bug. label Dec 6, 2022
@CbcWestwolf
Copy link
Member

/assign

@ti-chi-bot ti-chi-bot added may-affects-4.0 This bug maybe affects 4.0.x versions. may-affects-5.0 This bug maybe affects 5.0.x versions. may-affects-5.1 This bug maybe affects 5.1.x versions. may-affects-5.2 This bug maybe affects 5.2.x versions. may-affects-5.3 This bug maybe affects 5.3.x versions. may-affects-5.4 This bug maybe affects 5.4.x versions. may-affects-6.0 may-affects-6.1 may-affects-6.2 may-affects-6.3 may-affects-6.4 labels Dec 6, 2022
@ChenPeng2013 ChenPeng2013 removed may-affects-4.0 This bug maybe affects 4.0.x versions. may-affects-5.1 This bug maybe affects 5.1.x versions. may-affects-5.2 This bug maybe affects 5.2.x versions. may-affects-5.3 This bug maybe affects 5.3.x versions. may-affects-5.4 This bug maybe affects 5.4.x versions. may-affects-5.0 This bug maybe affects 5.0.x versions. may-affects-6.0 may-affects-6.1 may-affects-6.2 may-affects-6.3 may-affects-6.4 labels Dec 6, 2022
@Defined2014
Copy link
Contributor

Defined2014 commented Dec 7, 2022

Seems v6.1.x not support multi-schema change, we should split it to separate ddl statements.

@CbcWestwolf
Copy link
Member

Seems v6.1.x not support multi-schema change, we should split it to separate ddl statements.

Sure, it will be fixed by a later PR.

@CbcWestwolf
Copy link
Member

/close
Fixed by #39322

@ti-chi-bot
Copy link
Member

@CbcWestwolf: Closing this issue.

In response to this:

/close
Fixed by #39322

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
severity/critical sig/sql-infra SIG: SQL Infra type/bug The issue is confirmed as a bug.
Projects
None yet
Development

No branches or pull requests

5 participants