My Oracle Support Banner

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

Last updated on SEPTEMBER 09, 2021

Applies to:

MySQL Server - Version 8.0 and later
Information in this document applies to any platform.
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.

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 replica server in the replication can't be discovered or connected. For example:

>> Scenario 1

The source server in replication is running on host source.example.com with the default TCP port 3306. The replica server in the same replication is running on other host replica.example.com with the same TCP port 3306.
The adopting operation fails and shows that the replica server replica.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.