[jboss-jira] [JBoss JIRA] (JGRP-2092) MERGE3: merge never happens
Bela Ban (JIRA)
issues at jboss.org
Mon Sep 12 11:59:01 EDT 2016
[ https://issues.jboss.org/browse/JGRP-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13292055#comment-13292055 ]
Bela Ban edited comment on JGRP-2092 at 9/12/16 11:58 AM:
----------------------------------------------------------
[~ndillman] How did you arrive at this scenario? Did this happen in real life, or did you bring the system into this state on purpose, e.g. in testing?
I never thought of such a scenario, but of course I need to address it...
The first problem is that since nobody is the coordinator or its local view, nobody will start the view consistency checker task which checks for inconsistent views.
The second issue is that even if a view consistency check task was started (e.g. via JMX), it would run a similar check as the one above and never become the _merge leader_!
was (Author: belaban):
[~ndillman] How did you arrive at this scenario? Did this happen in real life, or did you bring the system into this state on purpose, e.g. in testing?
I never thought of such a scenario, but of course I need to address it...
> 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)
More information about the jboss-jira
mailing list