[jboss-jira] [JBoss JIRA] (JGRP-2412) GMS: reduce likelihood of merges on concurrent new member startup

[Bela Ban (Jira)]

    [ https://issues.redhat.com/browse/JGRP-2412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14007600#comment-14007600 ] 

Bela Ban commented on JGRP-2412:
--------------------------------

The discovered members during the JOIN process are cached now, so if we run multiple rounds (usually 1 is enough), the chances of everyone having the same set of members are high.

> GMS: reduce likelihood of merges on concurrent new member startup
> -----------------------------------------------------------------
>
>                 Key: JGRP-2412
>                 URL: https://issues.redhat.com/browse/JGRP-2412
>             Project: JGroups
>          Issue Type: Enhancement
>            Reporter: Bela Ban
>            Assignee: Bela Ban
>            Priority: Major
>             Fix For: 4.2.2, 5.0.0.Alpha4
>
>
> When multiple new members are started concurrently, and no coord is present yet, different clients get different discovery results, and this may lead to merging.
> If we have no coord, we could run the discovery protocol multiple time, *with the current members list being cached*, and then might end up with a more similar list of new members.
> This could be governed by an additional attribute in {{Discovery}} ({{num_discovery_runs}}?)



--
This message was sent by Atlassian Jira
(v7.13.8#713008)