The tables are in a transactionally consistent state on disk and you can copy the .ibd  tablespace files along with the corresponding .cfg  files to get a consistent snapshot of those tables. 

For the procedure to reimport the copied table data into a MySQL instance, see Section 15.6.1.3, “Importing InnoDB Tables” . 

After you are done with the tables, use UNLOCK TABLES  to release the locks, LOCK TABLES  to release the locks and acquire other locks, or START TRANSACTION  to release the locks and begin a new transaction. 

While any of these statements is in effect within the session, attempts to use FLUSH TABLES ... FOR EXPORT  produce an error: 

FLUSH TABLES ... WITH READ LOCK FLUSH TABLES ... FOR EXPORT LOCK TABLES ... READ LOCK TABLES ... WRITE 

While FLUSH TABLES ... FOR EXPORT  is in effect within the session, attempts to use any of these statements produce an error: 

## 13.7.8.4 KILL Statement 

FLUSH TABLES WITH READ LOCK FLUSH TABLES ... WITH READ LOCK FLUSH TABLES ... FOR EXPORT 

KILL [CONNECTION | QUERY] processlist_id 

Each connection to mysqld  runs in a separate thread. You can kill a thread with the KILL processlist_id  statement. 

Thread processlist identifiers can be determined from the ID  column of the INFORMATION_SCHEMA PROCESSLIST  table, the Id  column of SHOW PROCESSLIST  output, and the PROCESSLIST_ID column of the Performance Schema threads  table. The value for the current thread is returned by the CONNECTION_ID()  function. 

KILL  permits an optional CONNECTION  or QUERY  modifier: 

• KILL CONNECTION  is the same as KILL  with no modifier: It terminates the connection associated with the given processlist_id , after terminating any statement the connection is executing. 

• KILL QUERY  terminates the statement the connection is currently executing, but leaves the connection itself intact. 

The ability to see which threads are available to be killed depends on the PROCESS  privilege: 

•Without PROCESS , you can see only your own threads. 

•With PROCESS , you can see all threads. 

The ability to kill threads and statements depends on the CONNECTION_ADMIN  privilege and the deprecated SUPER  privilege: 

•Without CONNECTION_ADMIN  or SUPER , you can kill only your own threads and statements. 

•With CONNECTION_ADMIN  or SUPER , you can kill all threads and statements, except that to affect a thread or statement that is executing with the SYSTEM_USER  privilege, your own session must additionally have the SYSTEM_USER  privilege. 

