Mysql database is stuck in starting/initializing status after recovering from PITR
Description
Tested with Everest v0.5.0-49-gf4c8ffa release build version.
Install all operators. Create a 3 node myql database. Take manual and scheduled backups. Add data in the database. Enable PITR. Do a restore with PITR. After some more backups, disable PITR. Create multiple schedules and then enable PITR. Recover a database using PITR.
Mysql database details
Scheduled backups
Mongodb database is also created with backups
Postgresql database is also created with backups
Add some data in the postgresql database and restore it to another database, the restore is successful.
Recover the mysql database using PITR again. the database gets stuck in Initializing status
Scheduled backups get stuck in Unknown status
The dbr for mysql remained in Starting cluster status for a long time and then finally changed to Succeeded status after 121 minutes. Db status changes from restoring to initializing.
The pxc operator displays the following error:
However all haproxy and pxc pods seem fine
I can connect to the database and the db status seems fine
All the database backups taken
All logs for pxc pod, haproxy, pxc operator, everest operator, restore, pxc object, mysql object attached as db_stuck_initializing.tar.gz.
Environment
None
Attachments
11
Activity
Manish Chawla June 5, 2024 at 1:44 PM
Tested with Everest v0.11.0-rc1 version and did not observe the issue, hence will close it.
Tested with Everest v0.5.0-49-gf4c8ffa release build version.
Install all operators. Create a 3 node myql database. Take manual and scheduled backups. Add data in the database. Enable PITR. Do a restore with PITR. After some more backups, disable PITR. Create multiple schedules and then enable PITR. Recover a database using PITR.
Mysql database details
Scheduled backups
Mongodb database is also created with backups
Postgresql database is also created with backups
Add some data in the postgresql database and restore it to another database, the restore is successful.
Recover the mysql database using PITR again. the database gets stuck in Initializing status
Scheduled backups get stuck in Unknown status
The dbr for mysql remained in Starting cluster status for a long time and then finally changed to Succeeded status after 121 minutes. Db status changes from restoring to initializing.
The pxc operator displays the following error:
However all haproxy and pxc pods seem fine
I can connect to the database and the db status seems fine
All the database backups taken
All logs for pxc pod, haproxy, pxc operator, everest operator, restore, pxc object, mysql object attached as db_stuck_initializing.tar.gz.