MySQL Forums
Forum List  »  InnoDB clusters

We cannot add a new instance.
Posted by: 佳晃 富田
Date: January 05, 2020 07:42PM

Hello,

We are using MySQL InnoDB Cluster(version 8.0.18).
We are trying to add a new instance, '172.18.0.31:3306', but we cannot.



Before adding a new instance, clutser's status was shown as below:

-----------------------------------------------------------------------------
# mysqlsh

MySQL 172.18.0.32:33060+ ssl JS > cluster.status()
{
"clusterName": "testcluster",
"defaultReplicaSet": {
"name": "default",
"primary": "172.18.0.32:3306",
"ssl": "REQUIRED",
"status": "OK_NO_TOLERANCE",
"statusText": "Cluster is NOT tolerant to any failures.",
"topology": {
"172.18.0.32:3306": {
"address": "172.18.0.32:3306",
"mode": "R/W",
"readReplicas": {},
"replicationLag": null,
"role": "HA",
"status": "ONLINE",
"version": "8.0.18"
},
"172.18.0.33:3306": {
"address": "172.18.0.33:3306",
"mode": "R/O",
"readReplicas": {},
"replicationLag": null,
"role": "HA",
"status": "ONLINE",
"version": "8.0.18"
}
},
"topologyMode": "Single-Primary"
},
"groupInformationSourceMember": "172.18.0.32:3306"
}
-----------------------------------------------------------------------------



We checked the instance's configuration as below:

-----------------------------------------------------------------------------
MySQL 172.18.0.32:33060+ ssl JS > dba.checkInstanceConfiguration('root@172.18.0.31')

The instance '172.18.0.31:3306' is valid for InnoDB cluster usage.

{
"status": "ok"
}
-----------------------------------------------------------------------------


We did a adding instance command as below:

-----------------------------------------------------------------------------
MySQL 172.18.0.32:33060+ ssl JS > cluster.addInstance('root@172.18.0.31')
-----------------------------------------------------------------------------


And then, some messages were shown:

-------------------------------------------------------------------------------
NOTE: The target instance '172.18.0.31:3306' has not been pre-provisioned (GTID set
is empty). The Shell is unable to decide whether incremental distributed 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
'172.18.0.31:3306' with a physical snapshot from an existing cluster member. To
use this method by default, set the 'recoveryMethod' option to 'clone'.

The incremental distributed 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 Clone/ Incremental recovery / Abort (default Clone):
-----------------------------------------------------------------------------------


We selected a recovery method 'Clone', but some error messages were shown as below:

-------------------------------------------------------------------------------
Validating instance at 172.18.0.31:3306...

This instance reports its own address as 172.18.0.31:3306

Instance configuration is suitable.
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...

Cluster.addInstance: Recovery user 'rpl_user' not created by InnoDB Cluster (RuntimeError)
-------------------------------------------------------------------------------


In node '172.18.0.31', the 'rpl_user' was created at mysql.user table.
But we failed to add a instance, '172.18.0.31:3306'.

-------------------------------------------------------------------------------
MySQL 172.18.0.31:33060+ ssl SQL > select Host,User from mysql.user WHERE User = 'rpl_user';
+------------+----------+
| Host | User |
+------------+----------+
| 172.18.0.% | rpl_user |
+------------+----------+
-------------------------------------------------------------------------------


How can we resolve this problem ?
Please give us some advice.

Options: ReplyQuote


Subject
Views
Written By
Posted
We cannot add a new instance.
1104
January 05, 2020 07:42PM
426
January 06, 2020 11:28PM


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.