[jboss-jira] [JBoss JIRA] (JGRP-2237) The single node in the cluster not become a coordinator after coordinator leave.
Bela Ban (JIRA)
issues at jboss.org
Tue Nov 28 11:14:00 EST 2017
[ https://issues.jboss.org/browse/JGRP-2237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13494801#comment-13494801 ]
Bela Ban commented on JGRP-2237:
--------------------------------
Have you tried this with the config I attached (test.xml)? And please use the latest 4.0.8 to test; this is what I used and I never hit a problem.
Your log shows the member waited for 30s which is impossible as {{GMS.timeout}} is 3s in the config you attached! So either you used the wrong config, or attached the wrong config!
> 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)
More information about the jboss-jira
mailing list