MySQL Forums
Forum List  »  InnoDB clusters

Failed when adding instance to innodb cluster
Posted by: Jinwoo Jun
Date: December 28, 2022 05:43PM

I am facing fail when adding instance to innodb cluster.
I can't find a way to solve this problem.

Problem explain:
1. I prepared four VM(virutal machine) :
1 for MySQL Router : server name 'ic_r1'
3 for MySQL InnoDB Cluster : server anem 'ic_s1, s2, s3'

2. Install program ( program version : MySQL Community 8.0.31 )
ic_r1 : installed 'MySQL Shell'
ic_s1, s2, s3 : installed 'MySQL' and 'MySQL Shell'

3. make db user for InnoDB Cluster
create user 'cadmin' on ic_s1, s2, s3

4. Set configuration for ic_s1, s2, s3
dba.configureInstance(...)

5. create InnoDB Cluster on ic_s1
dba.createCluster(...)

6. add instance on created InnoDB Cluster : failed
. failed log
--------------------------------------------------------
MySQL khpesdb01mca01:33060+ ssl JS > cls.addInstance('cadmin@khpesdb03mca01')

NOTE: The target instance 'khpesdb03mca01:3306' has not been pre-provisioned (GTID set is empty). The Shell is unable to decide whether incremental state recovery can correctly provision it.
The safest and most convenient way to provision a new instance is through automatic clone provisioning, which will completely overwrite the state of 'khpesdb03mca01:3306' with a physical snapshot from an existing cluster member. To use this method by default, set the 'recoveryMethod' option to 'clone'.

The incremental state recovery may be safely used if you are sure all updates ever executed in the cluster were done with GTIDs enabled, there are no purged transactions and the new instance contains the same GTID set as the cluster or a subset of it. To use this method by default, set the 'recoveryMethod' option to 'incremental'.


Please select a recovery method [C]lone/ncremental recovery/[A]bort (default Clone): i
Validating instance configuration at khpesdb03mca01:3306...

This instance reports its own address as khpesdb03mca01:3306

Instance configuration is suitable.
NOTE: Group Replication will communicate with other members using 'khpesdb03mca01:3306'. Use the localAddress option to override.

A new instance will be added to the InnoDB cluster. Depending on the amount of
data on the cluster this might take from a few seconds to several hours.

Adding instance to the cluster...

ERROR: Unable to start Group Replication for instance 'khpesdb03mca01:3306'.
The MySQL error_log contains the following messages:
2022-12-27 08:24:09.369424 [System] [MY-013587] Plugin group_replication reported: 'Plugin 'group_replication' is starting.'
2022-12-27 08:24:09.380888 [System] [MY-010597] 'CHANGE MASTER TO FOR CHANNEL 'group_replication_applier' executed'. Previous state master_host='', master_port= 3306, master_log_file='', master_log_pos= 4, master_bind=''. New state master_host='<NULL>', master_port= 0, master_log_file='', master_log_pos= 4, master_bind=''.
2022-12-27 08:24:39.531922 [Error] [MY-011735] Plugin group_replication reported: '[GCS] Timeout while waiting for the group communication engine to be ready!'
2022-12-27 08:24:39.531981 [Error] [MY-011735] Plugin group_replication reported: '[GCS] The group communication engine is not ready for the member to join. Local port: 3306'
2022-12-27 08:24:39.577422 [Error] [MY-011735] Plugin group_replication reported: '[GCS] The member was unable to join the group. Local port: 3306'
2022-12-27 08:24:45.616098 [Error] [MY-011735] Plugin group_replication reported: '[GCS] Error connecting to all peers. Member join failed. Local port: 3306'
2022-12-27 08:24:45.661331 [Error] [MY-011735] Plugin group_replication reported: '[GCS] The member was unable to join the group. Local port: 3306'
2022-12-27 08:24:51.695701 [Error] [MY-011735] Plugin group_replication reported: '[GCS] Error connecting to all peers. Member join failed. Local port: 3306'
2022-12-27 08:24:51.738338 [Error] [MY-011735] Plugin group_replication reported: '[GCS] The member was unable to join the group. Local port: 3306'
2022-12-27 08:24:57.774530 [Error] [MY-011735] Plugin group_replication reported: '[GCS] Error connecting to all peers. Member join failed. Local port: 3306'
2022-12-27 08:24:57.821827 [Error] [MY-011735] Plugin group_replication reported: '[GCS] The member was unable to join the group. Local port: 3306'
2022-12-27 08:25:03.852152 [Error] [MY-011735] Plugin group_replication reported: '[GCS] Error connecting to all peers. Member join failed. Local port: 3306'
2022-12-27 08:25:03.899604 [Error] [MY-011735] Plugin group_replication reported: '[GCS] The member was unable to join the group. Local port: 3306'
2022-12-27 08:25:09.399855 [Error] [MY-011640] Plugin group_replication reported: 'Timeout on wait for view after joining group'
2022-12-27 08:25:09.399916 [Error] [MY-011735] Plugin group_replication reported: '[GCS] The member is already leaving or joining a group.'
2022-12-27 08:25:09.931778 [Error] [MY-011735] Plugin group_replication reported: '[GCS] Error connecting to all peers. Member join failed. Local port: 3306'
2022-12-27 08:25:09.976294 [Error] [MY-011735] Plugin group_replication reported: '[GCS] The member was unable to join the group. Local port: 3306'

---------------------------------

please give a hit to me.


thanks. jinwoo jun

Options: ReplyQuote


Subject
Views
Written By
Posted
Failed when adding instance to innodb cluster
510
December 28, 2022 05:43PM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.