Setting up replica 'jaytest-staging-002-usw2' of cluster 'jaytest-staging-002-use1' at instance '10.170.254.87:3306'. A new InnoDB Cluster will be created on instance '10.170.254.87:3306'. Validating instance configuration at 10.170.254.87:3306... This instance reports its own address as 10.170.254.87:3306 Instance configuration is suitable. NOTE: Group Replication will communicate with other members using '10.170.254.87:3306'. Use the localAddress option to override. * Checking transaction state of the instance... NOTE: A GTID set check of the MySQL instance at '10.170.254.87:3306' determined that it is missing transactions that were purged from all clusterset members. NOTE: The target instance '10.170.254.87:3306' has not been pre-provisioned (GTID set is empty). The Shell is unable to determine whether the instance has pre-existing data that would be overwritten with clone based recovery. Clone based recovery selected through the recoveryMethod option Waiting for clone process of the new member to complete. Press ^C to abort the operation. * Waiting for clone to finish... NOTE: 10.170.254.87:3306 is being cloned from 10.162.254.200:3306 ** Stage DROP DATA: Completed ** Clone Transfer FILE COPY ############################################################ 100% Completed PAGE COPY ############################################################ 100% Completed REDO COPY ############################################################ 100% Completed NOTE: 10.170.254.87:3306 is shutting down... * Waiting for server restart... ready * 10.170.254.87:3306 has restarted, waiting for clone to finish... ** Stage RESTART: Completed * Clone process has finished: 301.36 GB transferred in 1 hour 33 min 8 sec (53.93 MB/s) Creating InnoDB Cluster 'jaytest-staging-002-usw2' on '10.170.254.87:3306'... Adding Seed Instance... Cluster successfully created. Use Cluster.add_instance() to add MySQL instances. At least 3 instances are needed for the cluster to be able to withstand up to one server failure. * Configuring ClusterSet managed replication channel... ** Changing replication source of 10.170.254.87:3306 to 10.162.254.200:3306 * Waiting for instance '10.170.254.87:3306' to synchronize with PRIMARY Cluster... ** Transactions replicated ############################################################ 100% * Updating topology Replica Cluster 'jaytest-staging-002-usw2' successfully created on ClusterSet 'jaytest-staging-002'. Adding instance 10.170.255.88 to cluster jaytest-staging-002-usw2... WARNING: Using a password on the command line interface can be insecure. NOTE: A GTID set check of the MySQL instance at '10.170.255.88:3306' determined that it is missing transactions that were purged from all cluster members. NOTE: The target instance '10.170.255.88:3306' has not been pre-provisioned (GTID set is empty). The Shell is unable to determine whether the instance has pre-existing data that would be overwritten with clone based recovery. Clone based recovery selected through the recoveryMethod option Validating instance configuration at 10.170.255.88:3306... This instance reports its own address as 10.170.255.88:3306 Instance configuration is suitable. NOTE: Group Replication will communicate with other members using '10.170.255.88: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 enable clone on the instance '10.170.254.87:3306': MySQL Error 1290 (HY000): 10.170.254.87:3306: The MySQL server is running with the --super-read-only option so it cannot execute this statement ERROR: Unable to create the Group Replication recovery account: 10.170.254.87:3306: The MySQL server is running with the --super-read-only option so it cannot execute this statement Failed adding 10.170.255.88, continuing... Adding instance 10.170.255.223 to cluster jaytest-staging-002-usw2... WARNING: Using a password on the command line interface can be insecure. NOTE: A GTID set check of the MySQL instance at '10.170.255.223:3306' determined that it is missing transactions that were purged from all cluster members. NOTE: The target instance '10.170.255.223:3306' has not been pre-provisioned (GTID set is empty). The Shell is unable to determine whether the instance has pre-existing data that would be overwritten with clone based recovery. Clone based recovery selected through the recoveryMethod option Validating instance configuration at 10.170.255.223:3306... This instance reports its own address as 10.170.255.223:3306 Instance configuration is suitable. NOTE: Group Replication will communicate with other members using '10.170.255.223: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 enable clone on the instance '10.170.254.87:3306': MySQL Error 1290 (HY000): 10.170.254.87:3306: The MySQL server is running with the --super-read-only option so it cannot execute this statement ERROR: Unable to create the Group Replication recovery account: 10.170.254.87:3306: The MySQL server is running with the --super-read-only option so it cannot execute this statement Failed adding 10.170.255.223, continuing... WARNING: Using a password on the command line interface can be insecure. { "clusterName": "jaytest-staging-002-usw2", "defaultReplicaSet": { "name": "default", "primary": "10.170.254.87:3306", "ssl": "REQUIRED", "status": "OK_NO_TOLERANCE", "statusText": "Cluster is NOT tolerant to any failures.", "topology": { "10.170.254.87:3306": { "address": "10.170.254.87:3306", "instanceErrors": [ "ERROR: Unrecognized replication channel 'clusterset_replication' found. Unmanaged replication channels are not supported." ], "memberRole": "PRIMARY", "mode": "R/O", "readReplicas": {}, "replicationLag": "applier_queue_applied", "role": "HA", "status": "ONLINE", "version": "8.0.30" } }, "topologyMode": "Single-Primary" }, "groupInformationSourceMember": "10.170.254.87:3306"