Open cleverhu opened 2 years ago
The database should actually be created by the user, clusterpedia may not have the privilege to create the database.
At startup, clusterpedia creates the tables in the database.
Whether the database is deleted or the tables are deleted, we should stop all cluster synchro
and restart until the database is recreated or the tables are recreated by clusterpedia.
@cleverhu Are you willing to fix this problem?
Be careful not to coupling clusterpedia with internalstorage
It should be considered a feature rather than a bug, after all, the database/table being deleted manually at any time is already a production accident.
What happened?
When the database is deleted, syncmanager will not exit which results in no data acquisition.
What did you expect to happen?
When the database does not exist, the program needs to restart the syncmanger to create a new table.
How can we reproduce it (as minimally and precisely as possible)?
delete the mysql table manually.
Anything else we need to know?
No response
Clusterpedia Version
Host Kubernetes version