MySQL DBA Daily fault handling----Master-slave delay failure (171020)

Today after work received a database monitoring sent by the alarm message, the contents are as follows:

Server monitoring System DBA monitor V1.0

-------------------------------------------------------

Alarm server: **************

Alarm Host Name: **************:3306

-------------------------------------------------------

Alarm time: 2017-10-20-11:10:03

-------------------------------------------------------

Alarm content:

materid-185:mysql-bin.002114|391767716

slaveid-189:mysql-bin.002114|391767716|mysql-bin.002114|384247058|125

Analysis:

Through the alarm content we can find that this group of servers has a delay between the master and slave servers. From the alarm content can know the main binlog log and has synchronized to the Relay_log log point from the same, the log file is all but mysql-bin.002114 The log point is 391767716, but the slave does not have all the Rely-log logs restored, so it is likely that the Lord is performing a major transaction caused by the master-slave delay, through the analysis of the Lord's Binlog log can be found. In the Lord since 384247058 The log point does perform a large volume transaction operation.

Treatment scenario: Wait for natural recovery.

MySQL Course recommendations

MySQL performance management and architecture design

high-performance extensible MySQL Database design and Architecture Optimization e-commerce project  

MySQL Performance management and rack

This article is from the "DBA Log" blog, reproduced please contact the author!

MySQL DBA Daily fault handling----Master-slave delay failure (171020)