Bug #94060 MySQL Router depends on order without ORDER BY
Submitted: 25 Jan 2019 11:37 Modified: 24 May 2019 21:21
Reporter: Per Wilkås Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Router Severity:S3 (Non-critical)
Version:8.0.14 OS:Any
Assigned to: CPU Architecture:Any

[25 Jan 2019 11:37] Per Wilkås 
Description:
Noticed a lot of messages "Potential changes detected in cluster" in the router log file.
The SELECT statement in ClusterMetadata::fetch_instances_from_metadata_server does not specify ORDER BY and one of my nodes returns the rows in a different order.

How to repeat:
Don't know why the rows are returned in a different order.
[25 Jan 2019 12:40] MySQL Verification Team 
Hello Per Wilkås,

Thank you for the report.

regards,
Umesh
[24 May 2019 21:20] Philip Olson 
Posted by developer:
 
Fixed as of the upcoming MySQL Router 8.0.17 release, and here's the changelog entry:

Misleading "Potential changes detected in cluster" warnings were added to
Router's log file. Node order differences no longer cause these errors.

Thank you for the bug report.