Closed dschneller closed 5 years ago
We encountered the same issue where no secondary was set due to too high replication lag on both secondaries. In the previous state the consistent backup would simply crash with the error above, but after I patched it with the change by @dschneller it now gave us a clear message that the secondaries were lagging behind too far to be used.
The check was causing exceptions in case there was no secondary set due to the conditions before:
Added "is not None" to the check condition to ensure the score is only validated if a secondary is actually set.