The disaster caused by Mysqldump's Disable-keys

The mysqldump has a default parameter of Disable-keys, which is turned on by default.
This is not a problem in most cases, but in exceptional cases it can have disastrous consequences.

Recalled a few years ago, a well-known mobile phone forum Day inexplicable magic Brush does not open the Web page, finally no way to stop maintenance small half-day situation, according to the Grapevine, is the problem caused.

The whole process is guessed as follows:

1, their environment is still relatively standardized, with testing and online environment, developers in the test environment with tools to export a portion of the data, need to import into the online environment.
In addition, because of the forum, the current large replacement forum is the MyISAM table engine, this theory happens to be MyISAM (later explained why is MyISAM), laid the foundation of the disaster.

2, ordinary database, this method of operation is completely no problem, but this is a well-known forum, the number of visits is relatively large, the forum of a main table was executed Disable-keys, tragedy happened.




Other than that:
This situation is only for the MyISAM table, for the most use of InnoDB is not a problem.
For older systems such as the Discuz forum, it is important to note that importing data from different environments uses dump to export some of the data and then import it into another environment.

The--disable-keys=false can be used to avoid occurrence in accordance with the above conditions.

The disaster caused by Mysqldump's Disable-keys