[UI] Database does not come up if the number of nodes are changed
Description
Install all operators using cli on EKS. From the UI, create a mongodb database (default version 4.4) of 1 standalone small node. Edit the mongodb database and change the number of nodes from 1 to 3. The database doesn't come up and the cluster remains in Initializing state:
Create a mysql database of 1 standalone small node, version is 8.0.31-23.2. Create some data in the mysql database.
Edit the mysql database and change the number of nodes from 1 to 3. The database doesn't come up and the cluster remains in Initializing state:
Pod logs display:
This seems to be a mysql config issue with gcomm:// parameter used by the operator.
Environment
None
Attachments
3
Activity
Manish Chawla September 7, 2023 at 2:06 PM
Tested this on gke setup. I created one node mysql, mongo and postgresql databases and then upgraded them to 3 nodes. All the databases were able to come up successfully. Attaching database status of mysql and mongo db
Install all operators using cli on EKS. From the UI, create a mongodb database (default version 4.4) of 1 standalone small node.
Edit the mongodb database and change the number of nodes from 1 to 3. The database doesn't come up and the cluster remains in Initializing state:
Create a mysql database of 1 standalone small node, version is 8.0.31-23.2. Create some data in the mysql database.
Edit the mysql database and change the number of nodes from 1 to 3. The database doesn't come up and the cluster remains in Initializing state:
Pod logs display:
This seems to be a mysql config issue with gcomm:// parameter used by the operator.