Solve the Problem of mysql downtime

The possible cause of mysql downtime is the excessive amount of data. The mysql command can be identified but cannot be executed after it is entered. You need to: www.2cto.com 1, stop mysql2, in/etc/my. add innodb_force_recovery = 6 (as shown below) to the cnf file. InnoDB forcibly restores [mysqld] innodb_force_recovery = 4 (1-6) 1. innodb_force_recovery = 1. Even if the page is damaged, the server continues to run. This option is particularly useful for backing up or transferring the current data.
2. innodb_force_recovery = 2. Stop the master thread from running. If the master thread is cleared, the server will be suspended. 3. innodb_force_recovery = 3. Do not roll back the transaction after recovery. 4. innodb_force_recovery = 4. If the merge operation is inserted into the buffer zone, the system will crash and 5 innodb_force_recovery = 5 will not be executed. when starting the database, ignore UNDO log 6. innodb_force_recovery = 6. When you start the database, ignore rollback logs related to recovery 3, connect to mysql backup-related database 4, drop the backup database www.2cto.com 5, and recreate the database 6, remove innodb_force_recovery = 67, import the backup database, and solve the problem.