[
https://issues.jboss.org/browse/JGRP-2092?page=com.atlassian.jira.plugin....
]
Bela Ban edited comment on JGRP-2092 at 9/19/16 12:35 PM:
----------------------------------------------------------
OK, the issue has been resolved. The main changes are:
* MERGE3 now has all members (not just the coords) check for view inconsistencies if
{{only_coords_run_consistency_checker}} is false (default)
** (This is done every {{check_interval}} ms)
* To determine a merge leader, all actual coordinators are used. If this returns null
(because there are no coords), _all_ members will be used
* Participants (not just coordinators) are now also allowed to handle merges and install
merge views
was (Author: belaban):
OK, the issue has been resolved. The main changes are:
* MERGE3 now has all members (not just the coords) check for view inconsistencies if
{{only_coords_run_consistency_checker}} is false (default)
** (This is done every {{check_interval}} ms)
* To determine a merge leader, all actual coordiantors are used. If this returns null
(because there are no coords), _all_ members will be used
* Participants (not just coordinators) are now also allowed to handle merges and install
merge views
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)