Table 'mysql.bind_info' doesn't exist causes TiDB to fail to start

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

Original topic: Table ‘mysql.bind_info’ doesn’t exist 导致TiDB无法启动

| username: Miracle

[TiDB Usage Environment] Production Environment / Test / Poc

[TiDB Version]

[Reproduction Path] What operations were performed when the issue occurred
TiDB is deployed on three nodes in a K8S cluster. It was upgraded about two months ago, and everything was normal until recently. One of the nodes was restarted recently, and after it came back up, TiDB failed to start, reporting that the bind_info table was missing. Later, another node also went down due to full disk space, causing another TiDB instance to fail.

[Encountered Problem: Problem Phenomenon and Impact]
Is there any way to recover?

[Resource Configuration]
[Attachments: Screenshots / Logs / Monitoring]
[2022/11/14 13:36:34.623 +08:00] [INFO] [base_client.go:104] [“[pd] init cluster id”] [cluster-id=7146020452736557313]
[2022/11/14 13:36:34.623 +08:00] [INFO] [client.go:648] [“[pd] tso dispatcher created”] [dc-location=global]
[2022/11/14 13:36:34.629 +08:00] [INFO] [store.go:80] [“new store with retry success”]
[2022/11/14 13:36:34.645 +08:00] [INFO] [tidb.go:72] [“new domain”] [store=tikv-7146020452736557313] [“ddl lease”=45s] [“stats lease”=3s] [“index usage sync lease”=0s]
[2022/11/14 13:36:34.962 +08:00] [INFO] [domain.go:169] [“full load InfoSchema success”] [currentSchemaVersion=0] [neededSchemaVersion=621] [“start time”=267.754682ms]
[2022/11/14 13:36:34.968 +08:00] [INFO] [domain.go:432] [“full load and reset schema validator”]
[2022/11/14 13:36:34.968 +08:00] [INFO] [ddl.go:347] [“[ddl] start DDL”] [ID=c378d589-4d5b-4024-8382-a88b784aa976] [runWorker=true]
[2022/11/14 13:36:34.968 +08:00] [INFO] [manager.go:189] [“start campaign owner”] [ownerInfo=“[ddl] /tidb/ddl/fg/owner”]
[2022/11/14 13:36:34.972 +08:00] [INFO] [ddl.go:336] [“[ddl] start delRangeManager OK”] [“is a emulator”=false]
[2022/11/14 13:36:34.972 +08:00] [INFO] [ddl_worker.go:156] [“[ddl] start DDL worker”] [worker=“worker 1, tp general”]
[2022/11/14 13:36:34.972 +08:00] [INFO] [ddl_worker.go:156] [“[ddl] start DDL worker”] [worker=“worker 2, tp add index”]
[2022/11/14 13:36:34.986 +08:00] [FATAL] [terror.go:292] [“unexpected error”] [error=“[schema:1146]Table ‘mysql.bind_info’ doesn’t exist”]

| username: buddyyuan | Original post link

Manually rebuild this table. Besides the old binding being gone, there shouldn’t be any major impact.

| username: Miracle | Original post link

Uh, TiDB won’t start, how do I rebuild it?

| username: erwadba | Original post link

You should be able to perform scaling operations. First, take the TiDB node offline, and then scale it out later.

| username: tidb狂热爱好者 | Original post link

It should be that the MySQL user table was accidentally imported during the import process.

| username: system | Original post link

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