[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
Thu Dec 14 04:02:00 EST 2017
[ https://issues.jboss.org/browse/JGRP-2237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13505365#comment-13505365 ]
Bela Ban commented on JGRP-2237:
--------------------------------
I wrote a simple program which continually disconnects and then reconnects the coordinator (bla3, attached). I ran it for over a 1000 disconnect/reconnect sequences and it never failed.
Run it yourself (change the path to the properties), to see if it fails.
{noformat}
-------------------------------------------------------------------
GMS: address=A, cluster=demo, physical address=127.0.0.1:7800
-------------------------------------------------------------------
-- view: [B|1071] (2) [B, A]
-- view: [A|1072] (1) [A]
-- view: [A|1073] (2) [A, B]
{noformat}
> 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: Server_A.txt, Server_A_Trace_mode.rtf, Server_B.txt, Server_B_Trace_mode.rtf, conf.txt, 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