[
https://jira.jboss.org/jira/browse/JGRP-735?page=com.atlassian.jira.plugi...
]
Bela Ban commented on JGRP-735:
-------------------------------
Okay, I added num_initial_srv_members. Here's how the algorithm works:
If num_initial_srv_members > 0:
- Return as soon as we have the specified number of *server* responses (from members
which already joined)
Else return as soon as we have num_initial_members responses (clients or servers).
Note that if break_on_coord_rsp is true, then we terminate the discovery phase and return
as soon as we have 1 coord response
Docu is at
http://wiki.jboss.org/auth/wiki/JGroupsPING.
Discovery: ignore discovery responses from clients
--------------------------------------------------
Key: JGRP-735
URL:
https://jira.jboss.org/jira/browse/JGRP-735
Project: JGroups
Issue Type: Feature Request
Reporter: Bela Ban
Assignee: Bela Ban
Priority: Minor
Fix For: 2.7
If we have 9 joining members (starting simultaneously) and 1 operational member X, and
num_initial_rsps=5 and
timeout=3000
,then a joining member might receive 5 responses from other joining clients and *not* the
one from the existing member.
This is good when we have *initial* concurrent startups, but not when we have existing
'well-known' operational members running.
FEATURE: add a flag 'ignore-client-responses' which will collect only responses
from operational members (servers). In the above case, each joining member will either get
a response from X, or time out after 5 secs. We could also define a min_operational_resps,
which (enabled if > 0) defines the minimum number of responses which need to be
received from operational member and ignores responses from client members.
WORKAROUND: increase num_initial_mbrs and timeout
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira