What is the workflow flow chart and main steps of Mydumper
Mydumper work flow chart and what are the main steps, I believe that many inexperienced people do not know what to do, so this paper summarizes the causes of the problem and solutions, through this article I hope you can solve this problem.
Workflow flow chart:
The main steps are summarized:
1. The main thread FLUSH TABLES WITH READ LOCK, which imposes a global read-only lock to prevent DML statements from being written and to ensure data consistency
two。 Read the binary log file name and the location of log writes at the current point in time and record them in the metadata file for even point recovery
3. N (the number of threads can be specified, default is 4) dump thread START TRANSACTION WITH CONSISTENT SNAPSHOT; turn on things that read the same
4.dump non-InnoDB tables, which first exports the table of the non-transaction engine
5. After the backup of the main thread UNLOCK TABLES non-transaction engine, release the global read-only lock
6.dump InnoDB tables, deriving InnoDB tables based on things
7. Things are over.
Back up the generated files
All the backup files are in one directory, which can be specified by yourself.
The directory contains a metadata file
Records the binary log file name of the backup database at the backup time point and the location where the log is written
If you are backing up from the slave library, you will also record the binary log files synchronized to the primary library and the write location during the backup.
Each table has two backup files:
Database.table-schema.sql structure file
Database.table.sql data file
If you slice a table file, multiple backup data files will be generated, and you can specify the number of rows or specify the size of the shard
After reading the above, have you mastered the Mydumper work flow chart and what are the main steps? If you want to learn more skills or want to know more about it, you are welcome to follow the industry information channel, thank you for reading!
