You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In some cases it is possible for PostgreSQL replication slots [1] to exist without having the changes they track consumed.
This can happen if a HA standby server fails and is not brought back online or if a global region database is not responding.
This is fairly simple to check for by inspecting the pg_replication_slots view's "active" column [2]. I'm suggesting that ManageIQ/CFME implement some monitoring for inactive replication slots and raise an event/notification if they persist for some set amount of time.
This issue has been automatically marked as stale because it has not been updated for at least 3 months.
If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.
Thank you for all your contributions! More information about the ManageIQ triage process can be found in the traige process documentation.
BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1445291
In some cases it is possible for PostgreSQL replication slots [1] to exist without having the changes they track consumed.
This can happen if a HA standby server fails and is not brought back online or if a global region database is not responding.
This is fairly simple to check for by inspecting the pg_replication_slots view's "active" column [2]. I'm suggesting that ManageIQ/CFME implement some monitoring for inactive replication slots and raise an event/notification if they persist for some set amount of time.
[1] https://www.postgresql.org/docs/9.5/static/warm-standby.html#STREAMING-REPLICATION-SLOTS
[2] https://www.postgresql.org/docs/9.5/static/view-pg-replication-slots.html
The text was updated successfully, but these errors were encountered: