[
https://issues.jboss.org/browse/JGRP-2237?page=com.atlassian.jira.plugin....
]
Bela Ban commented on JGRP-2237:
--------------------------------
The {{VERIFY_SUSPECT}} timeout of 10s sometimes prevented a member from getting removed
from the view *before* the other member was restarted. The other issue was that your
{{port_range}} is 0, which means not all members will be probed for, ie. discovered
sometimes.
I attached the correct config, run a diff to your config to see the differences.
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)