[
https://issues.jboss.org/browse/JGRP-2237?page=com.atlassian.jira.plugin....
]
Bela Ban commented on JGRP-2237:
--------------------------------
So if we look at the view changes, the following happens: {{654}} is the first member,
then {{11729}} joins. Next, {{654}} (the coord) leaves. Then, {{28153}} joins, but becomes
singleton as it doesn't get a discovery response from {{11729}}.
This could be because of a misconfig; again. I tried my {{test.xml}} with {{master}} at
least 30 times, and it always worked, and views were created correctly.
The single node in the cluster not become a coordinator after
coordinator leave.
--------------------------------------------------------------------------------
Key: JGRP-2237
URL:
https://issues.jboss.org/browse/JGRP-2237
Project: JGroups
Issue Type: Bug
Affects Versions: 4.0.2, 4.0.8
Reporter: kfir avraham
Assignee: Bela Ban
Priority: Minor
Attachments: test.xml
I got cluster with 2 members, sometimes when the first node (coordinator) leave the
cluster the second one is not become a coordinator.
When the first one is rejoin, he could not determine coordinator and select new one from
the nodes list.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)