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
We found a bug in repmgrd process. Whenever a primary database host is hung (Not able to perform any DML/DDL operations), the repmgrd process on the HA is running but not updating the log files. It is stuck
repmgrd process in Sleep state on standby:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
249678 postgres 20 0 87312 10604 7324 S 0.0 0.0 1334:46 /usr/pgsql-15/bin/repmgrd -f /postgres/admin/pgrepmgr/5304/pgrepmgr_5304.conf —log-level DEBUG —daemonize
When we see the connections on the Primary, the repmgr process (of the standby ) is stuck in trying to INSERT data into repmgr.monitoring_history table.
During this situation there is no autofailover, Is this a known issue? how can we make sure that repmgrd does auto failover in such situations?
Thanks,
Nikhil
The text was updated successfully, but these errors were encountered:
Hi, i had a similar issue some time ago, resulting in "monitoring_history requested but primary connection not available" entries on the standby while no failover was happening (and therefore repmgrd continued to sleep). Since i had restarted repmgrd regularly, this didn't happen anymore. I not yet tried if this is still an issue in newer versions.
Stephan
Hi repmgr team,
We found a bug in repmgrd process. Whenever a primary database host is hung (Not able to perform any DML/DDL operations), the repmgrd process on the HA is running but not updating the log files. It is stuck
repmgrd process in Sleep state on standby:
When we see the connections on the Primary, the repmgr process (of the standby ) is stuck in trying to INSERT data into repmgr.monitoring_history table.
During this situation there is no autofailover, Is this a known issue? how can we make sure that repmgrd does auto failover in such situations?
Thanks,
Nikhil
The text was updated successfully, but these errors were encountered: