[MXS-2223] Additional logging when dealing with delayed slaves Created: 2018-12-13  Updated: 2019-02-04  Resolved: 2019-02-04

Status: Closed
Project: MariaDB MaxScale
Component/s: Core, readwritesplit
Affects Version/s: 2.2.17
Fix Version/s: 2.3.4

Type: Task Priority: Major
Reporter: Valerii Kravchuk Assignee: Esa Korhonen
Resolution: Fixed Votes: 0
Labels: None

Sprint: MXS-SPRINT-73, MXS-SPRINT-74

 Description   

When detect_replication_lag setting is used, it would be great to have a way to get the following information recorded in Maxscale log:

1) Seconds behind master (or exact delay) as detected by Maxscale when there is a lag
2) Time when read connections are routed to Master because of delay
3) Time when read connections are routed back to slave (they are within allowed delay)


Generated at Thu Feb 08 04:12:34 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.