content_image/661473.jpg
If necessary, you can stop a cloning operation with a KILL QUERY processlist_id  statement. 

On the recipient MySQL server instance, you can retrieve the processlist identifier (PID) for a cloning operation from the PID  column of the clone_status  table. 

mysql> SELECT * FROM performance_schema.clone_status\G *************************** 1. row *************************** ID: 1 PID: 8 STATE: In Progress BEGIN_TIME: 2019-07-15 11:58:36.767 END_TIME: NULL SOURCE: LOCAL INSTANCE DESTINATION: / path/to/clone_dir / ERROR_NO: 0 ERROR_MESSAGE: BINLOG_FILE: BINLOG_POSITION: 0 GTID_EXECUTED: 

You can also retrieve the processlist identifier from the ID  column of the INFORMATION_SCHEMA PROCESSLIST  table, the Id  column of SHOW PROCESSLIST  output, or the PROCESSLIST_ID  column of the Performance Schema threads  table. These methods of obtaining the PID information can be used on the donor or recipient MySQL server instance. 

## 5.6.7.11 Clone System Variable Reference 

<img src='content_image/661473.jpg'>

## 5.6.7.12 Clone System Variables 

This section describes the system variables that control operation of the clone plugin. If values specified at startup are incorrect, the clone plugin may fail to initialize properly and the server does not load it. In this case, the server may also produce error messages for other clone settings because it does not recognize them. 

Each system variable has a default value. System variables can be set at server startup using options on the command line or in an option file. They can be changed dynamically at runtime using the SET statement, which enables you to modify operation of the server without having to stop and restart it. 

