Converting Asynchronous Replication Setup to InnoDB Cluster Causes the Status to Always be "(MISSING)" After Adding Previous Replication Slaves
Last updated on DECEMBER 05, 2017
Applies to:MySQL Server - Version 5.7 and later
Information in this document applies to any platform.
When attempting to convert a traditional asynchronous replication setup into an InnoDB Cluster, the status of the secondary nodes ends up being (MISSING) instead of ONLINE.
The issue can for example be seen using the following steps:
- Start with a setup of a replication master and one or more replication slaves.
- Create the InnoDB Cluster using the replication master node, for example:
An asynchronous replication setup has been converted into InnoDB Cluster.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms