Differences

This shows you the differences between two versions of the page.

--- resolution_area:prometheus_resolutions:res-p1706 [2021/06/25 10:09] – external edit 127.0.0.1
+++ resolution_area:prometheus_resolutions:res-p1706 [2021/12/16 17:01] (current) – 10.91.120.28
@@ Line 6: / Line 6: @@
 **Purpose:**
-**Scenario:** MysqL replication lag on <server> for 5m .
+**Scenario:** This can occur when there are additional processes running on the DB servers e.g key_stats or the database backups. Processes like these typically lock rows and cause replication to lag or fail.
-**Resolution:**
+**Resolution:** If key stats is running, try to give it some time to complete its process, replication should resume when these processes have been completed, likewise with the DB backups. You must keep an eye on this though, sometimes when the process completes replication does not restart. In this instance, intervention is needed.
-**Manual Action Steps:**
+**Manual Action Steps:** If replication fails to come back after the processes on the DB blocking it. Stop and start the slave process on DB2, in most instances, this will resolve the problem. If after this it still does not start, check the last occurred error in the slave status to see the reported problem. In this instance, skipping this update would be required.
-**Auto Clear:**
+**Auto Clear:** Yes

Internal Errigal Collaboration Wiki