My Oracle Support Banner

Converting Asynchronous Replication Setup to InnoDB Cluster Causes the Status to Always be "(MISSING)" After Adding Previous Replication Replicas (Doc ID 2336074.1)

Last updated on DECEMBER 07, 2021

Applies to:

MySQL Server - Version 5.7 and later
Information in this document applies to any platform.

Symptoms

Disclaimer: Starting from v8.0, some terms have been deprecated. Older releases will only use the deprecated terminology, and new releases will only use new terminology. Please see https://dev.mysql.com/doc/mysqld-version-reference/en/ for a complete list of those changes, and in which minor versions it happened.

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:

  1. Start with a setup of a replication source and one or more replication replicas.
  2. Create the InnoDB Cluster using the replication source node, for example:

 

Changes

An asynchronous replication setup has been converted into InnoDB Cluster.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.