[jgroups-users] Unexpected Merge, Coordinator in multiple partitions

Hi JGroups Users,

We have seen an unexpected Merge View in one of our deployments, where the coordinator is in multiple partitions.
And I am not really sure if this is a bug or a feature (TM).

The situation is like this:
Members: [A,B,C] 
Subgroup 1: [A,B,C]
Subgroup 2: [A,B]

We would have expected to see:
Members: [A,B,C] 
Subgroup 1: [A,B]
Subgroup 2: [C]

It also looks like Node C has been isolated from A,B but the isolation ended before Node C changed its View.
With a View like this is it hard on Node C to detect that there has been a certain change in the topology,
especially if the coordinator (A) is in the major and in the minor partition.

Has anyone seen similar behaviour or an idea how to prevent a Merge situation like this ?

A small example project which reproduces the mentioned behaviour can be downloaded here: 
https://www.dc-square.de/wp-content/uploads/jgroups-test.zip


Regards,
Christoph
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot