Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
2.5.8
-
None
Description
The max_slave_replication_lag parameter was changed in 2.5 to interpret the value as the limit under which the replication lag must fall. This seems to have been broken by a merge and it now behaves as it did in 2.4.