MySQL Forums
Forum List  »  InnoDB clusters

Re: clone results original .ibd file disappeared
Posted by: MIN SOO CHO
Date: August 29, 2019 03:06AM

I tried another approach, Just make cluster and add instance. Following logs shows what I did.

MySQL localhost:33060+ ssl JS > dba.checkInstanceConfiguration('root@mysqlgr2:3306')^C
MySQL localhost:33060+ ssl JS > dba.configureInstance('root@mysqlgr2:3306')
Configuring MySQL instance at mysqlgr2:3306 for use in an InnoDB cluster...

This instance reports its own address as mysqlgr2:3306
Clients and other cluster members will communicate with it through this address by default. If this is not correct, the report_host MySQL system variable should be changed.

NOTE: Some configuration options need to be fixed:
+--------------------------+---------------+----------------+--------------------------------------------------+
| Variable | Current Value | Required Value | Note |
+--------------------------+---------------+----------------+--------------------------------------------------+
| binlog_checksum | CRC32 | NONE | Update the server variable |
| enforce_gtid_consistency | OFF | ON | Update read-only variable and restart the server |
| gtid_mode | OFF | ON | Update read-only variable and restart the server |
| server_id | 1 | <unique ID> | Update read-only variable and restart the server |
+--------------------------+---------------+----------------+--------------------------------------------------+

Some variables need to be changed, but cannot be done dynamically on the server.
Do you want to perform the required configuration changes? [y/n]: y
Do you want to restart the instance after configuring it? [y/n]: y
Configuring instance...
The instance 'mysqlgr2:3306' was configured for InnoDB cluster usage.
Restarting MySQL...
ERROR: Remote restart of MySQL server failed: MySQL Error 3707 (HY000): Restart server failed (mysqld is not managed by supervisor process).
Please restart MySQL manually
MySQL localhost:33060+ ssl JS > dba.checkInstanceConfiguration('root@mysqlgr2:3306')
Validating MySQL instance at mysqlgr2:3306 for use in an InnoDB cluster...

This instance reports its own address as mysqlgr2:3306
Clients and other cluster members will communicate with it through this address by default. If this is not correct, the report_host MySQL system variable should be changed.

Checking whether existing tables comply with Group Replication requirements...
No incompatible tables detected

Checking instance configuration...
Instance configuration is compatible with InnoDB cluster

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

{
"status": "ok"
}
MySQL localhost:33060+ ssl JS > cluster.addInstance('root@mysqlgr2:3306')

NOTE: The target instance 'mysqlgr2: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
'mysqlgr2: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 [C]lone/ncremental recovery/[A]bort (default Clone): C
Validating instance at mysqlgr2:3306...

This instance reports its own address as mysqlgr2: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...

Monitoring recovery process of the new cluster member. Press ^C to stop monitoring and let it continue in background.
Clone based state recovery is now in progress.

NOTE: A server restart is expected to happen as part of the clone process. If the
server does not support the RESTART command or does not come back after a
while, you may need to manually start it back.

* Waiting for clone to finish...
NOTE: mysqlgr2:3306 is being cloned from mysqlgr1:3306
** Stage DROP DATA: Failed
** Clone Transfer
FILE COPY ============================================================ 0% Not Started
PAGE COPY ============================================================ 0% Not Started
REDO COPY ============================================================ 0% Not Started
ERROR: The clone process has failed: Clone Donor Error: 1016 : Can't open file: './testdb/hello.ibd' (errno: 2 - No such file or directory). (3862)
Cluster.addInstance: Clone Donor Error: 1016 : Can't open file: './testdb/hello.ibd' (errno: 2 - No such file or directory). (RuntimeError)
MySQL localhost:33060+ ssl JS >

Options: ReplyQuote


Subject
Views
Written By
Posted
Re: clone results original .ibd file disappeared
584
August 29, 2019 03:06AM


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.