Bug 488660

Summary: Documentation for heartbeats -- add to the cluster chapter
Product: Red Hat Enterprise MRG Reporter: Carl Trieloff <cctrieloff>
Component: DocumentationAssignee: Andrew Stitcher <astitcher>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Jeff Needle <jneedle>
Severity: medium Docs Contact:
Priority: medium    
Version: 1.1CC: lbrindle
Target Milestone: 1.3Keywords: Documentation
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-09-10 03:56:40 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Carl Trieloff 2009-03-05 03:27:47 UTC
Heartbeat can be configured to allow clients to detect when a broker has failed and connect to another broker or cluster member.Heartbeats are sent by the broker at a client specified, per-connection frequency. If the client does not receive a heartbeat or any other traffic for two heartbeat intervals, the connection will be made to fail.

What would happen when there is a no heartbeat within a predefined interval?

If there is no traffic for two heartbeat intervals, the client will fail the connection. The application will see the exact same response as when the connection is killed.

What happens if the broker is unable to send heartbeat?

As above, if there is no other traffic the client will eventually kill the connection.

Does the client retry?

You can control the heartbeat interval on the client through the heartbeat member of ConnectionSettings (it is measured in seconds). Some of the options on policies do vary for different clients.

Comment 1 Lana Brindley 2009-03-09 01:09:56 UTC
Need setup and configuration information, and usage examples (if possible).

Thanks,
LKB

Comment 2 Carl Trieloff 2009-03-30 12:48:58 UTC
Assigning to Andrew to provide C++ configuration info,

then assign to Rafi to provide Java configuration info.