You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2023/03/08 11:53:00 UTC

[jira] [Work logged] (ARTEMIS-3640) external clients cannot use cluster topology for HA or load balancing

     [ https://issues.apache.org/jira/browse/ARTEMIS-3640?focusedWorklogId=849785&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-849785 ]

ASF GitHub Bot logged work on ARTEMIS-3640:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 08/Mar/23 11:52
            Start Date: 08/Mar/23 11:52
    Worklog Time Spent: 10m 
      Work Description: gtully commented on PR #4394:
URL: https://github.com/apache/activemq-artemis/pull/4394#issuecomment-1460043242

    w.r.t to doc, HA=true is really Pair Affinity = true. This feature allows a client url to respect the affinity but to override the url.




Issue Time Tracking
-------------------

            Worklog Id:     (was: 849785)
    Remaining Estimate: 0h
            Time Spent: 10m

> external clients cannot use cluster topology for HA or load balancing
> ---------------------------------------------------------------------
>
>                 Key: ARTEMIS-3640
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-3640
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>            Reporter: Vilius Šumskas
>            Assignee: Gary Tully
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Let's say there is a simple Artemis HA master/slave shared storage cluster with such configuration:
>  
> {noformat}
> <connectors>
>    <connector name="artemis-master">tcp://internal-cluster-dns-1:61616</connector>
>    <connector name="artemis-slave">tcp://internal-cluster-dns-2:61616</connector>
> </connectors>
> {noformat}
> The cluster is using static discovery.
>  
> Factory on internal clients are using:
> {noformat}
> (tcp://internal-cluster-dns-1:61616,tcp://internal-cluster-dns-2:61616)?ha=true&reconnectAttempts=30&useTopologyForLoadBalancing=false{noformat}
> Those internal clients can successfully connect to the cluster and failover works as expected.
>  
> However if there is also external clients which use external DNS/IP address of the cluster the topology doesn't return correct DNS name and the failover fails.
> {noformat}
> (tcp://external-cluster-dns-1:61616,tcp://external-cluster-dns-2:61616)?ha=true&reconnectAttempts=30&useTopologyForLoadBalancing=false{noformat}
> {noformat}
> org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnector: AMQ214033: Cannot resolve host java.net.UnknownHostException: internal-cluster-dns-1{noformat}
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)