Description

Symptoms: GAB errors “Excessive delay between successive calls to GAB heartbeat” seen in engine log while running a single node/standalone VCS cluster where GAB is disabled.

Description: GAB heartbeat log messages are logged as an information when there is delay between heartbeats(had being stuck). In case of ‘had’ running in ‘-onenode’, GAB need not be enabled. When ‘had’ is running in ‘-onenode’; For self-check purpose, ‘had’ simulates heartbeat with an internal component of ‘had’ itself. These log messages are logged because of delay in simulated heartbeats.

Resolution: Log messages seen are for informational purpose only. When ‘had’ is running in ‘-onenode’, no action will be taken on excessive delay between heartbeats

G lobal Atomic Broadcast simulator (GABSIM) does not take any action if the High Availability Daemon (HAD) is unable to maintain heartbeat. To clarify, the “excessive delay” message is logged by HAD when the delay in heartbeat is more than 5 seconds. HAD logs the message irrespective of whether it has  registered with GAB or GABSIM. The delay of 5 seconds is not configurable.
There is no tunable to turn off the logging. At this point all we can sugest is  upgradeing the system resources if possible to reduce the logs