-
Notifications
You must be signed in to change notification settings - Fork 13.1k
Description
In Nacos 2.5.1, the provided mysql-schema.sql file no longer contains the creation statement for the config_info_beta table, which exists in previous versions such as 2.5.0.
This omission leads to runtime side effects:
Nacos executes the following SQL as part of its internal database health check:
SELECT * FROM config_info_beta WHERE id = 1;
If the config_info_beta table is missing, the query fails and logs the following error:
[db-error] master db xxx.xxx.xxx.xxx down.
These logs appear in:
logs/nacos-persistence.log
However, the actual MySQL database is working fine — the failure is caused by a missing table, not a real connection issue.
Steps to Reproduce:
Deploy Nacos 2.5.1 with an external MySQL instance.
Use the official conf/mysql-schema.sql file to initialize the database (note: config_info_beta table is missing).
Start Nacos.
Observe the following logs:
ERROR [db-error] master db xxx.xxx.xxx.xxx down.
Additional Context:
After manually creating the config_info_beta table (using the SQL from 2.5.0), the health check log errors stop appearing.
This confirms the issue is due to the missing table in the schema file, not an actual database failure.
Environment Info:
Item | Version
Nacos | 2.5.1
MySQL | 8.0.33
Deploy Method | Docker
JDBC Mode | External MySQL
Affected Files | conf/mysql-schema.sql, logs/nacos-persistence.log
Thanks for your attention!