With the poolnodes command, one of the standby nodes shows as UP, but also has high replication delay, e.g.:
/db/data directory and sub-files have the correct postgres:users ownership.
Identity Manager 3.3.7
PostgreSQL database replication de-synchronization on the affected vIDM node.
Manually trigger a database re-sync for the affected node using the pcp_recovery_node utility.
Obtain the specific node ID of the delayed node from the poolnodes output.
Execute the following command to force the re-sync, replacing <FAILED_NODE_ID> with the actual ID:
/usr/local/bin/pcp_recovery_node -w -h localhost -U pgpool -p 9898 -n 0
Confirm again with the poolnodes command that the replication delay is gone, e.g.: