repmgr 4.2 Documentation | |||
---|---|---|---|
Prev | Up | Chapter 21. BDR failover with repmgrd | Next |
Register both nodes; example on node1:
$ repmgr -f /etc/repmgr.conf bdr register NOTICE: attempting to install extension "repmgr" NOTICE: "repmgr" extension successfully installed NOTICE: node record created for node 'node1' (ID: 1) NOTICE: BDR node 1 registered (conninfo: host=node1 dbname=bdrtest user=repmgr)
and on node1:
$ repmgr -f /etc/repmgr.conf bdr register NOTICE: node record created for node 'node2' (ID: 2) NOTICE: BDR node 2 registered (conninfo: host=node2 dbname=bdrtest user=repmgr)
The repmgr extension will be automatically created when the first node is registered, and will be propagated to the second node.
Important: Ensure the repmgr package is available on both nodes before attempting to register the first node.
At this point the meta data for both nodes has been created; executing repmgr cluster show (on either node) should produce output like this:
$ repmgr -f /etc/repmgr.conf cluster show ID | Name | Role | Status | Upstream | Location | Connection string ----+-------+------+-----------+----------+-------------------------------------------------------- 1 | node1 | bdr | * running | | default | host=node1 dbname=bdrtest user=repmgr connect_timeout=2 2 | node2 | bdr | * running | | default | host=node2 dbname=bdrtest user=repmgr connect_timeout=2
Additionally it's possible to display log of significant events; executing repmgr cluster event (on either node) should produce output like this:
$ repmgr -f /etc/repmgr.conf cluster event Node ID | Event | OK | Timestamp | Details ---------+--------------+----+---------------------+---------------------------------------------- 2 | bdr_register | t | 2017-07-27 17:51:48 | node record created for node 'node2' (ID: 2) 1 | bdr_register | t | 2017-07-27 17:51:00 | node record created for node 'node1' (ID: 1)
At this point there will only be records for the two node registrations (displayed here in reverse chronological order).