repmgr 5.1 : wal replay pending on standby
Closed this issue · 1 comments
Restored primary to PIT from backup. Ran pg_wal_replay_resume once restore completed and primary was in "normal" mode as expected. Cloned standby from primary using following
==> repmgr -h -f /etc/repmgr/12/repmgr.conf -U repmgr -d repmgr standby clone --dry-run
WARNING: following problems with command line parameters detected:
"config_directory" set in repmgr.conf, but --copy-external-config-files not provided
NOTICE: destination directory "/pgDATA/data" provided
INFO: connecting to source node
DETAIL: connection string is: host= user=repmgr dbname=repmgr
DETAIL: current installation size is 167 GB
INFO: "repmgr" extension is installed in database "repmgr"
INFO: parameter "max_replication_slots" set to 10
INFO: parameter "max_wal_senders" set to 12
NOTICE: checking for available walsenders on the source node (2 required)
INFO: sufficient walsenders available on the source node
DETAIL: 2 required, 12 available
NOTICE: checking replication connections can be made to the source server (2 required)
INFO: required number of replication connections could be made to the source server
DETAIL: 2 replication connections required
INFO: replication slots will be created by user "repmgr"
NOTICE: standby will attach to upstream node 1
HINT: consider using the -c/--fast-checkpoint option
INFO: all prerequisites for "standby clone" are met
repmgr -h -f /etc/repmgr/12/repmgr.conf -U repmgr -d repmgr standby clone after the dry run completed without any errors.
The standby started successfully
postgres=# SELECT pg_is_in_recovery();
pg_is_in_recovery
t
(1 row)
==> repmgr service status
ID | Name | Role | Status | Upstream | repmgrd | PID | Paused? | Upstream last seen
----+---------------+---------+-----------+---------------+---------+--------+---------+--------------------
1 | node 1 | primary | * running | | running | 7568 | no | n/a
2 | node 2 | standby | running | primary_node | running | 114477 | no | 1 second(s) ago
WARNING: following issues were detected
- WAL replay is paused on node "secondary_node" (ID: 2) with WAL replay pending; this node cannot be manually promoted until WAL replay is resumed
What am i missing to resume streaming replication?
self solve