[jboss-jira] [JBoss JIRA] (JGRP-2237) The single node in the cluster not become a coordinator after coordinator leave.

kfir avraham (JIRA) issues at jboss.org
Wed Nov 29 07:52:00 EST 2017


    [ https://issues.jboss.org/browse/JGRP-2237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13495192#comment-13495192 ] 

kfir avraham commented on JGRP-2237:
------------------------------------

i attached another logs in trace mode, you can see from 'Nov-29-2017 *+00:24:08+* GMT-12:00 [org.jgroups.protocols.TCP] [TcpServer.Acceptor[8102]-5,clm-tlv-spih62-62502] [TRACE] - 10.63.16.13:8102: rejected connection from 10.63.16.3:8102  (connection existed and my address won as it's higher)'



> 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