[jboss-jira] [JBoss JIRA] Commented: (JGRP-735) Discovery: ignore discovery responses from clients

[Vladimir Blagojevic (JIRA)]

    [ https://jira.jboss.org/jira/browse/JGRP-735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12430084#action_12430084 ] 

Vladimir Blagojevic commented on JGRP-735:
------------------------------------------

Lowest impact solution satisfying all of the above mentioned options is introduction of response_ratio (servers/clients) parameter and use it in combination with existing num_initial_rsps. response_ratio of 1 means that all num_initial_rsps responses must come from servers while response_ratio of 0 waits for num_initial_rsps either client or server responses. default is 0.

> 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