Bug #96491 MySQL Shell overwrites metadata information
Submitted: 9 Aug 2019 15:29 Modified: 14 Aug 2019 8:43
Reporter: Pedro Pinheiro Email Updates:
Status: Verified Impact on me:
None 
Category:Shell AdminAPI InnoDB Cluster / ReplicaSet Severity:S3 (Non-critical)
Version:8.0.17 OS:Any
Assigned to: CPU Architecture:Any

[9 Aug 2019 15:29] Pedro Pinheiro
Description:
Hi,
While trying to setup a two cluster connected with async replication, as described here:
https://lefred.be/content/mysql-innodb-cluster-with-2-data-centers-for-disaster-recovery-h...

it was found out that creating the second site DC2 in Node 4 overwrites the existing meta-data, meaning in step:
-------
We can verify in the InnoDB Cluster Metadata that we have 2 clusters now:
-------

We only see one cluster and note two, that results in being impossible to connect the two cluster using ASYNC Repl between them.

Using MySQL Shell 8.0.15 this problem does not exist.

How to repeat:
Execute the steps described in https://lefred.be/content/mysql-innodb-cluster-with-2-data-centers-for-disaster-recovery-h...

Suggested fix:
Should be possible to deploy two geo redundant clusters, using the steps described in https://lefred.be/content/mysql-innodb-cluster-with-2-data-centers-for-disaster-recovery-h...

Or even better, the scenario of two Geo-Redundant InnoDB Cluster should be deployed and managed automatically.
[14 Aug 2019 8:43] MySQL Verification Team
Dear Pedro,

Thank you for the report and feedback.

regards,
Umesh