Bug 592358 - Document behavior if --cluster-size is specified.
Document behavior if --cluster-size is specified.
Status: CLOSED DUPLICATE of bug 598653
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: Messaging_Programming_Reference (Show other bugs)
All Linux
medium Severity medium
: 1.3
: ---
Assigned To: Jonathan Robie
MRG Quality Engineering
Depends On:
  Show dependency treegraph
Reported: 2010-05-14 12:02 EDT by Alan Conway
Modified: 2013-08-05 20:54 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-06-01 15:32:39 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Alan Conway 2010-05-14 12:02:40 EDT
The documentation needs to cover this:

If --cluster-size=N is specified then the cluster will not become active until it has N members. This is useful if your cluster members have persistent stores, since it allows all the members to compare the status and select the correct store image to start up with.

If a client connects to the cluster while there are < N members, the client will hang opening the connection until all N members have joined the cluster, then it will proceed as normal. 

If connection heartbeats are enabled they can interrupt this hang XREF to heartbeats
Comment 1 ppecka 2010-05-17 11:03:09 EDT
please check https://bugzilla.redhat.com/show_bug.cgi?id=592995 also
Comment 2 Alan Conway 2010-06-01 15:32:39 EDT

*** This bug has been marked as a duplicate of bug 598653 ***

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