MySQL crash: InnoDB redo log error Solution

Source: Internet
Author: User


MySQL crash: InnoDB redo log error solution InnoDB: Progress in percents: 1120731 9:56:59 InnoDB: Error: page 9 log sequence number 5746244819174 InnoDB: is in the future! Current system log sequence number 5706919300319. innoDB: Your database may be created upt or you may have copied the InnoDBInnoDB: tablespace but not the InnoDB log files. ======================================== innodb redo log error www.2cto.com cause: unknown solution: After MHA switches to the backup host, the host is restored and the binlog on the backup host is aligned with the data, it is added as the backup host. author ylqmf

Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.