Rechercher dans le manuel MySQL
21.6.4 Adopting an Existing Replication Set Up
As an alternative to creating a new InnoDB ReplicaSet, you can
also adopt an existing replication setup using the
adoptFromAR
option with
dba.createReplicaSet()
. The replication setup
is scanned, and if it is compatible with the InnoDB ReplicaSet
prerequisites, AdminAPI creates the necessary metadata. Once
the replication setup has been adopted, you can only use
AdminAPI to administer the InnoDB ReplicaSet.
To convert an existing replication setup to a InnoDB ReplicaSet connect to the primary, also referred to as the master. The replication topology is automatically scanned and validated, starting from the instance MySQL Shell's global session is connected to. The configuration of all instances is checked during adoption, to ensure they are compatible with InnoDB ReplicaSet usage. All replication channels must be active and their transaction sets as verified through GTID sets must be consistent. The data set of all instances are expected to be identical, but is not verified. All instances that are part of the topology are automatically added to the replica set. The only changes made by this operation to an adopted replica set are the creation of the metadata schema. Existing replication channels are not changed during adoption, although they could be changed during subsequent primary switch operations.
For example, to adopt a replication topology consisting of the
MySQL server instances on example1
and
example2
to an InnoDB ReplicaSet, connect
to the primary at example1
and issue:
mysql-js> rs = dba.createReplicaSet('testadopt', {'adoptFromAR':1})
A new replicaset with the topology visible from 'example1:3306' will be created.
* Scanning replication topology...
** Scanning state of instance example1:3306
** Scanning state of instance example2:3306
* Discovering async replication topology starting with example1:3306
Discovered topology:
- example1:3306: uuid=00371d66-3c45-11ea-804b-080027337932 read_only=no
- example2:3306: uuid=59e4f26e-3c3c-11ea-8b65-080027337932 read_only=no
- replicates from example1:3306
source="localhost:3310" channel= status=ON receiver=ON applier=ON
* Checking configuration of discovered instances...
This instance reports its own address as example1:3306
example1:3306: Instance configuration is suitable.
This instance reports its own address as example2:3306
example2:3306: Instance configuration is suitable.
* Checking discovered replication topology...
example1:3306 detected as the PRIMARY.
Replication state of example2:3306 is OK.
Validations completed successfully.
* Updating metadata...
ReplicaSet object successfully created for example1:3306.
Use rs.add_instance() to add more asynchronously replicated instances to
this replicaset and rs.status() to check its status.
Once the InnoDB ReplicaSet has been adopted, you can use it in the same way that you would use a replica set which was created from scratch. From this point you must administer the InnoDB ReplicaSet using only AdminAPI.
Document created the 26/06/2006, last modified the 26/10/2018
Source of the printed document:https://www.gaudry.be/en/mysql-rf-replicaset-adopting.html
The infobrol is a personal site whose content is my sole responsibility. The text is available under CreativeCommons license (BY-NC-SA). More info on the terms of use and the author.
References
These references and links indicate documents consulted during the writing of this page, or which may provide additional information, but the authors of these sources can not be held responsible for the content of this page.
The author This site is solely responsible for the way in which the various concepts, and the freedoms that are taken with the reference works, are presented here. Remember that you must cross multiple source information to reduce the risk of errors.