[
https://issues.jboss.org/browse/JGRP-2092?page=com.atlassian.jira.plugin....
]
Bela Ban commented on JGRP-2092:
--------------------------------
Hi [~ndillman]
{quote}
We no longer see the issue as it was worked around with staggering responses for all of
the "bulk response" messages (ie: view change, etc).
{quote}
This may have reduced the chances of such a scenario happening, but I don't think it
eliminated it completely. In my next comment, I'll show how such a scenario can be
reproduced.
Yes, a solution will involve a non-coordinator becoming merge leader, but this requires
code changes in 3 places: the merge detection, the merge leader determination and the
actual merge merge.
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)