Automatic Failover with ACM

The failover mechanism relies on periodic checks of the following shared status file:

/opt/aspera/acm/run/acm4orchestrator.status

By default, the status file is kept up-to-date by the active node changing its last modification date every minute. The status file expires if there is no update by the active node within the last two minutes.

One of two situations will occur when a status file expires:

• If the active node detects that the status file is expired, it automatically updates it.
• If the passive node detects that the status file is expired, it assumes that the peer node is out of service and performs an automatic failover.
  Note: Automatic failover will only occur if the MySQL database is stopped on the peer node; otherwise, the failover will not be triggered.