Bug 488660 - Documentation for heartbeats -- add to the cluster chapter
Summary: Documentation for heartbeats -- add to the cluster chapter
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: Documentation
Version: 1.1
Hardware: All
OS: Linux
medium
medium
Target Milestone: 1.3
: ---
Assignee: Andrew Stitcher
QA Contact: Jeff Needle
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-03-05 03:27 UTC by Carl Trieloff
Modified: 2010-09-10 03:56 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-09-10 03:56:40 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.