fix: failed to read replication lag: cannot assign NULL to int

Description

We get an error if the sync instance (for some reason) is not in recovery mode, since the request in this case returned NULL.

Fixed:

2022/09/23 18:52:51 retrieval_status.go:108: [WARNING] Failed to fetch replication lag failed to read replication lag: can't scan into dest[0]: cannot assign NULL to *int

Related issue

Examples

Checklist

• MR description has been reviewed
• MR changes are functionally tested
• MR does NOT have text changes OR there are text changes and they have been reviewed
• MR does NOT have API/CLI changes OR there are API/CLI changes and they have been reviewed
• MR does NOT have UI changes OR there are UI changes and they have been reviewed

requested review from @akartasov, @NikolayS, and @fomin.list

assigned to @vitabaks

approved this merge request

merged

mentioned in commit b73f2ec9

mentioned in issue #479 (closed)