Postgres as a Service
Deploy a Managed Postgres Cluster in Minutes! Enterprise-ready and Oracle compatible.
Failover Manager provides the efm utility to assist with cluster management.efm add-node cluster_name ip_address [priority]Invoke the efm add-node command to allow the specified node to join the cluster. Provide the name of the cluster, the IP address of the joining node, and (if the new node is a Standby server) the priority in which it will be promoted.Include a priority value if the node being added is a standby node. The value specifies the order in which the new node will be used in the event of a failover. priority is an integer value of 1 to n, where n is the number of standby nodes in the list. Specify a value of 1 to indicate that the new node is the primary standby, and will be the first node promoted in the event of a failover.If you do not specify a priority when adding a Standby agent, the node will be added to the end of the priority list. A standby cannot be excluded from the priority list by omitting the priority value - all standbys are candidates for promotion. To add a node that cannot be promoted, start the node as a witness.This command must be invoked by efm or root.efm cluster-status cluster_nameInvoke the efm cluster-status command to display the status of a Failover Manager cluster. For more information about the cluster status report, see Section 4.2.1.efm cluster-status-json cluster_nameInvoke the efm cluster-status-json command to display the status of a Failover Manager cluster in json format. While the format of the displayed information is different than the display generated by the efm cluster-status command, the information source is the same.efm encrypt cluster_nameInvoke the efm encrypt command to encrypt the database password before include the password in the cluster properties file.efm prop-check cluster_nameThe efm prop-check command invokes a utility that may help to identify configuration problems caused by mismatched property files.When invoked on the Witness node with a cluster named employees, the prop-check command might display:# efm prop-check employees
Binding address: 172.24.38.107
I am witness node: true
Cluster name: employees
User email: email@example.com
Automatic failover set to: true
Network adapters: eth0
127.0.0.1efm promote cluster_nameThe promote command instructs Failover Manager to perform a manual failover of master to standby. This command must be invoked by efm or root.Manual promotion should only be attempted if the status command reports that the cluster includes a Standby node that is up-to-date with the Master. If there is no up-to-date Standby, Failover Manager will prompt you before continuing.Please note that this command instructs the service to ignore the value specified in the auto.failover parameter in the cluster properties file.efm remove-node cluster_name ip_addressInvoke the efm remove-node command to remove the specified node from the allowed hosts list, and prevent the node from joining a cluster. This command also removes the cluster from the failover priority list. Provide the name of the cluster and the IP address of the node when calling the efm remove-node command. This command must be invoked by efm or root.efm resume cluster_nameInvoke the efm resume command to resume monitoring a previously stopped database. This command must be invoked by efm or root.efm stop-cluster cluster_nameInvoke the efm stop-cluster command to stop Failover Manager on all nodes. This command instructs Failover Manager to connect to each node on the cluster and instruct the existing members to shut down. The command has no effect on running databases, but when the command completes, there is no failover protection in place. This command must be invoked by efm or root.Invoke the efm --help command to display online help for the Failover Manager utility commands.