Table of Contents Previous Next


2 Failover Manager - Overview : 2.3 Tutorial – Configuring a Simple Failover Manager Cluster

The cluster_name.properties file contains parameters that specify connection properties and behaviors for your Failover Manager cluster. Modifications to property settings are applied when Failover Manager starts.
Owner of the data directory (usually postgres or enterprisedb):
Set this property to true on a witness node and false if it is a master or standby:
Please note that the Failover Manager agent will not verify the content of the efm.nodes file; the agent expects that some of the addresses in the file cannot be reached (e.g. that another agent hasn’t been started yet). For more information about the efm.nodes file, see Section 3.5.2.
Copy the efm.properties and efm.nodes files to the /etc/edb/efm-3.2 directory on the other nodes in your sample cluster. After copying the files, change the file ownership so the files are owned by efm:efm. The efm.properties file can be the same on every node, except for the following properties:
Modify the bind.address property to use the node’s local address.
Set is.witness to true if the node is a witness node. If the node is a witness node, the properties relating to a local database installation will be ignored.
On any node, start the Failover Manager agent. The agent is named efm-3.2; you can use your platform-specific service command to control the service. For example, on a CentOS or RHEL 7.x host use the command:
Start the agent on the other nodes. Run the efm cluster-status efm command on any node to see the cluster status.
For more information about using the efm command line tool, see Section 5.3.

2 Failover Manager - Overview : 2.3 Tutorial – Configuring a Simple Failover Manager Cluster

Table of Contents Previous Next