[ClusterLabs] PAF fails to promote slave: Can not get current node LSN location

Tiemen Ruiten t.ruiten at tech-lab.io
Wed Jul 10 11:08:45 EDT 2019

On Wed, Jul 10, 2019 at 2:47 PM Jehan-Guillaume de Rorthais <jgdr at dalibo.com>

> >
> > I double-checked monitoring data: there was approximately one minute of
> > replication lag on one slave and two minutes of replication lag on the
> > other slave when the original issue occurred.
> what lag? current primary LSN versus sent, received, synced or replayed?

Replay, I use pg_last_xact_replay_timestamp to monitor lag.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20190710/bccb0caf/attachment.html>

More information about the Users mailing list