[jboss-jira] [JBoss JIRA] (JGRP-2092) MERGE3: merge never happens

[Bela Ban (JIRA)]

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

Bela Ban commented on JGRP-2092:
--------------------------------

A simple way to fix this would be to take the first members (coords) of all subviews and have them run the merge. In the Sept 12 example, this would be the set \{A,B,C\}. However, this would mean that _participants_ (not _coordinators_) would be able to run the show, ie. install new views, which is something that JGroups hasn't liked so far.

I need to think about whether anyone being able to install new views is a security risk...

Also, MERGE3 would have everyone run the ConsistencyChecker task, and not just the coordinators.

Perhaps this additional behavior can be enabled via an attribute (in GMS and MERGE3). By default, it would be true, so participants are allowed to run merges and install views. If this turns out to cause no problems over a couple of releases, we can remove the flag again...

> MERGE3: merge never happens
> ---------------------------
>
>                 Key: JGRP-2092
>                 URL: https://issues.jboss.org/browse/JGRP-2092
>             Project: JGroups
>          Issue Type: Bug
>            Reporter: Bela Ban
>            Assignee: Bela Ban
>             Fix For: 3.6.11, 4.0
>
>         Attachments: jgroups.txt
>
>
> (Reported by Neal Dillman)
> In the case below, a merge doesn't seem to happen. Write a unit test to reprodue this.
> {noformat}
> Host A view: B, X, Y, Z, A  (where B should be coordinator)
> Host B view: C, Q, R, S, B (where C should be coordinator)
> Host C view: A, M, N, O, C (where A should be coordinator)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)