[jira] [Commented] (ARTEMIS-3157) uneven number of connections in a cluster

["Justin Bertram (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ARTEMIS-3157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17412697#comment-17412697 ] 

Justin Bertram commented on ARTEMIS-3157:
-----------------------------------------

Can you reproduce this on a simpler configuration (e.g. 2 live brokers, no backups)?

Also, is there any functional impact?

> uneven number of connections in a cluster
> -----------------------------------------
>
>                 Key: ARTEMIS-3157
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-3157
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 2.17.0
>            Reporter: Erwin Dondorp
>            Priority: Major
>
> Using a cluster of 3 master + 3 slave nodes. full interconnect, each with a fresh virtual disk. no other constructions (bridges/federation/brokerconn/etc) and also no clients.
> On each master nodes, the 2 static connections to the other master nodes are visible, and each is marked with the dedicated cluster username. so that part seems ok.
> but without any clients having connected, there are additional connections. the amount is not the same in each master node. Some connections show "127.0.0.1" as address, something that is not in my configuration. none of the extra connections have any sessions. Also the connections do not have any sessions.
> the details of an example:
>  * broker1: 3 connections to own slave; 2 extra to/from broker2; 1 extra to/from backup of broker3
>  * broker2: 3 connections to own slave; 2 extra to/from broker1; 2 extra to/from broker3; 1 extra to/from slave of broker3
>  * broker3: 1 connection to own slave; no other extra connections
> the exact amount of connections varies a little between startups and also seems to depend on the exact startup sequence.
> my assumption is that these connections should not be present, and that this is not intended, hence this report. my wild guess is that these are remnants from connections that did not succeed due to the other cluster-members not fully available yet.
> When the cluster is started one node at a time, the effect seems to exists only on the first node that was started.
> Note: not related to ARTEMIS-2870 as this report is still valid in 2.18.0-20210322.234647-43.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)