Bug #98870 Description about MySQL Router is wrong
Submitted: 9 Mar 2020 6:04 Modified: 1 Oct 2020 18:11
Reporter: AKIHIRO IKEZOE Email Updates:
Status: Closed Impact on me:
Category:MySQL Router Severity:S3 (Non-critical)
Version:8.0.19 OS:Any
Assigned to: CPU Architecture:Any

[9 Mar 2020 6:04] AKIHIRO IKEZOE
The following document describes the behavior of MySQL Router.
I think this description is wrong.
MySQL Router can automatically detect additional instances and we need not restart MySQL Router.


> When MySQL Router is bootstrapped against a cluster, it records the server instance's addresses in its configuration file. If any additional instances are added to the cluster after bootstrapping the MySQL Router, they are not automatically detected and therefore are not used for connection routing.

> To ensure that newly added instances are routed to correctly you must bootstrap MySQL Router against the cluster to read the updated metadata. This means that you must restart MySQL Router and include the --bootstrap option.

How to repeat:
See above.

Suggested fix:
Fix the document to "MySQL Router can automatically detect additional instances and we need not restart MySQL Router."
[11 Mar 2020 12:41] MySQL Verification Team
Hello AKIHIRO-San,

Thank you for the report and feedback.

[23 Sep 2020 15:53] Gaurav Kumar Garg
Is it fine if i can start working on this, to go first ?
[23 Sep 2020 16:46] Gaurav Kumar Garg
@Akihiro Ikezoe

Do you have separate source code for documentation ? I did not found it in mysql-server code base.
[1 Oct 2020 18:11] Philip Olson
Posted by developer:
This bug was closed in the past, the exact timing is unknown.

Thank you for reporting this bug; it appears there was a delay in documenting the dynamic state feature.