EnterpriseDB/repmgr

node check fail on witness

Closed this issue · 3 comments

repmgr 5.1 running repmgr node check on witness node fail in case there no upstream configured.

$ repmgr node check
Node "10.54.110.83":
        Server role: OK (node is witness)
        Replication lag: OK (N/A - node is witness)
        WAL archiving: OK (0 pending archive ready files)
        Upstream connection: CRITICAL (node "10.54.110.83" (ID: 3) is not attached to expected upstream node "10.54.110.162" (ID: 1))
        Downstream servers: OK (this node has no downstream nodes)
        Replication slots: OK (node has no physical replication slots)
        Missing physical replication slots: OK (node has no missing physical replication slots)
        Configured data directory: OK (configured "data_directory" is "/var/lib/postgresql/9.6/twenty")

Expected: Upstream connection: OK (N/A - node is witness)

Fixed:

$ repmgr node check
Node "node3":
        Server role: OK (node is witness)
        Replication lag: OK (N/A - node is witness)
        WAL archiving: OK (0 pending archive ready files)
        Upstream connection: OK (N/A - node is a witness)
        Downstream servers: OK (N/A - node is a witness)
        Replication slots: OK (node has no physical replication slots)
        Missing physical replication slots: OK (node has no missing physical replication slots)
        Configured data directory: OK (configured "data_directory" is "/home/postgres/repmgr-test/node_3/data")
$ echo $?
0

Thanks for the report!

Closing as issue resolved and no further response received after.

Fix will be included in the next repmgr release (date to be determined).

TiTi commented

Looking forward a CentOS/RHEL release with this fix!
For now we stay on 5.0.0