MySQL Bugs: #98893: MySQL Router docker should use MYSQL_INNODB_CLUSTER

Bug #98893	MySQL Router docker should use MYSQL_INNODB_CLUSTER_MEMBERS as lower limit
Submitted:	10 Mar 2020 15:46	Modified:	30 Apr 2020 4:33
Reporter:	Nir Gilboa	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Package Repos	Severity:	S3 (Non-critical)
Version:	8.0.19	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
This report refers to the docker image available at:
https://hub.docker.com/r/mysql/mysql-router

Description:
The run.sh script wait for an exact match between the number of healthy nodes in the cluster and the variable value given by MYSQL_INNODB_CLUSTER_MEMBERS.

How to repeat:
Scenario:
1. Healthy InnoDB Cluster with 2 nodes
2. Bring up the router with MYSQL_INNODB_CLUSTER_MEMBERS = 1.
The following will appear in the log at bootstrap:

Waiting for 1 cluster instances to become available via <ipaddr> (1/12)
...

Suggested fix:
Make MYSQL_INNODB_CLUSTER_MEMBERS a lower limit, or make the error indicate clearly that it should be an exact match. (which doesn't make a lot of sense imho)

Hello Nir Gilboa,

Thank you for the report and feedback.

regards,
Umesh