Changing the remote agent heartbeat interval
Remote agents periodically send a "heartbeat" signal to the Bamboo server. This is vital for tracking whether your remote agents are online or offline. The remote heartbeat is asynchronous, which means that if a remote agent goes offline and comes back online again it will reconnect instead of being shut down (as long as the same server is available).
However, you may wish to adjust the time parameters for the remote agent heartbeat, particularly if you have a lot of network activity already.
There are three configurable parameters on the bamboo server for the remote agent heartbeat:
The frequency of the heartbeat signal from remote agents. The value is in seconds.
The default value is 60 seconds.
How long the Bamboo server will wait before it times out an agent that it hasn't received a heartbeat signal from. A remote agent that has been timed out will be marked as 'Offline'. Any builds being run by agents which have timed out will be abandoned. The value is in seconds.
The default value is 600 seconds.
How often Bamboo checks for agents that have exceeded the heartbeat timeout specified in
bamboo.agent.heartbeatTimeoutSeconds. The value is in seconds.
The default value is 30 seconds.
The parameters above are passed as JVM parameters. We recommend to add these options using the variable JVM_SUPPORT_RECOMMENDED_ARGS defined in the file <Bamboo install directory>/bin/setenv.sh.
See Configuring Bamboo on startup for instructions on how to change a Bamboo system property.
Was this helpful?Yes Provide feedback about this article