You have a consistent InnoDB backup created with mysqldump, the largest table is 50 GB in size.
You start to restore your backup with this command;
shell> mysql –u root –p < backup.sql
After 30 minutes, you notice that the rate of restore seems to have slowed down. No other processes or external factors are affecting server performance.
Which is the most likely explanation for this slowdown?

A. The MySQL server has stopped inserting data to check index consistency.
B. InnoDB is doing CRC32 checks over the tablespace data as it grows.
C. The MySQL server is taking a periodical snapshot of data so it can resume the restore if it is interrupted mid-way.
D. InnoDB has filled the redo log and now must flush the pages.
E. Secondary indexes no longer fit into the buffer pool.
Answer: D

InnoDB将当前redo log写满了，必须其将脏页flush到磁盘http://www.cndba.cn/hbhe0316/article/22769

版权声明：本文为博主原创文章，未经博主允许不得转载。

MYSQL