My Oracle Support Banner

Target Slave Can't Be Discovered Or Connected While Creating A New InnoDB ReplicaSet By Adopting An Existing Replication (Doc ID 2674142.1)

Last updated on MAY 26, 2020

Applies to:

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

Symptoms

When adopting an existing replication setup using the adoptFromAR option with dba.createReplicaSet() in MySQL Shell to create a new InnoDB ReplicaSet, the operation may fails and shows that the target slave server in the replication can't be discovered or connected. For example:

>> Scenario 1

The master server in replication is running on host master.example.com with the default TCP port 3306. The slave server in the same replication is running on other host slave.example.com with the same TCP port 3306.
The adopting operation fails and shows that the slave server slave.example.com can't be discovered:

 

Changes

 Adopt a normal running asynchronous replication using the adoptFromAR option with dba.createReplicaSet() in MySQL Shell to create a new InnoDB ReplicaSet.

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.