Heartbeat detection determines how often the cluster’s name servers test whether each server is online. When the name server detects a server has gone offline, it stops directing IIOP clients to that server.
Heartbeat detection affects only IIOP clients and interserver calls. If you partition components, that is, you do not install all components into every server, interserver calls are required when a component calls another components that is not available on the same server. In these cases, enable heartbeat detection and tune the test interval. A shorter interval minimizes the chance that clients attempt to connect to servers that have gone offline, but if the interval is too short, you can waste resources with excessive broadcasting from the name servers to the member servers. The default of two minutes works well for most applications.
If your application does not have any IIOP clients or use interserver calls, you can disable heartbeat detection in EAServer. (Note HTTP client load balancing and failover are performed outside of EAServer.)
To change these setting in EAServer Manager, follow the instructions in “Heartbeat detection” in Chapter 6, “Clusters and Synchronization,” in the EAServer System Administration Guide. To change this setting with jagtool, use the set_props command to set these properties for the primary server:
Synchronize the cluster after modifying these settings.
