Controlling the Failover Manager Service v4
Each node in a Failover Manager cluster hosts a Failover Manager agent that is controlled by a service script. By default, the service script expects to find:
- A configuration file named
efm.propertiesthat contains the properties used by the Failover Manager service. Each node of a replication scenario must contain a properties file that provides information about the node.
- A cluster members file named
efm.nodesthat contains a list of the cluster members. Each node of a replication scenario must contain a cluster members list.
Note that if you are running multiple clusters on a single node you will need to manually create configuration files with cluster-specific names and modify the service script for the corresponding clusters.
The commands that control the Failover Manager service are platform-specific.
On RHEL/CentOS 7.x and RHEL/CentOS 8.x, Failover Manager runs as a Linux service named (by default)
edb-efm-4.2.service that is located in
/usr/lib/systemd/system. Each database cluster monitored by Failover Manager will run a copy of the service on each node of the replication cluster.
Use the following systemctl commands to control a Failover Manager agent that resides on a RHEL/CentOS 7.x and RHEL/CentOS 8.x host:
The start command starts the Failover Manager agent on the current node. The local Failover Manager agent monitors the local database and communicates with Failover Manager on the other nodes. You can start the nodes in a Failover Manager cluster in any order. This command must be invoked by root.
Stop the Failover Manager on the current node. This command must be invoked by root.
The status command returns the status of the Failover Manager agent on which it is invoked. You can invoke the status command on any node to instruct Failover Manager to return status and server startup information.