Data Repository Heartbeat Monitor Process

The heartbeat monitor process checks whether the data repository is running every 10 seconds.
The heartbeat monitor process checks whether the data repository is running every 10 seconds. If the heartbeat process fails to confirm that the database is running after 5 minutes, the data aggregator shuts down. An audit message is logged in the
<installation_directory>
/
<apache-karaf-*
/shutdown.log
file.
  • installation_directory
    The installation directory of the data aggregator.
    Default:
    /opt
  • apache-karaf-*
    The installation directory for Apache Karaf.
    Example:
    apache-karaf-4.2.6
In a cluster environment,
DX NetOps Performance Management
checks the availability of the nodes in the cluster continuously every 10 seconds. If
DX NetOps Performance Management
cannot contact a node within 5 minutes, it generates and logs an event.
DX NetOps Performance Management
logs an audit message in the
shutdown.log
file.
If the data repository node that failed is the primary node, the data aggregator automatically switches to the next available node.
DX NetOps Performance Management
generates and logs an event.
DX NetOps Performance Management
interrupts certain administrative functions that occur during a high-availability failover, and then they fail. One poll cycle is lost. These functions do not resume after the data repository connects to another node in the cluster environment. The administrative functions that you perform after the data repository connects to another node in the cluster environment work as designed.
If more than one data repository node fails, the data aggregator shuts down.
The data aggregator shuts down automatically if it fails to connect to the data repository on start-up.