You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@artemis.apache.org by "Vilius Šumskas (Jira)" <ji...@apache.org> on 2026/04/14 10:54:00 UTC

[jira] [Created] (ARTEMIS-6004) Allow manual definition of cluster topology server list

Vilius Šumskas created ARTEMIS-6004:
---------------------------------------

             Summary: Allow manual definition of cluster topology server list
                 Key: ARTEMIS-6004
                 URL: https://issues.apache.org/jira/browse/ARTEMIS-6004
             Project: Artemis
          Issue Type: New Feature
            Reporter: Vilius Šumskas


Let’s say there is a HA cluster with one primary and one backup node, with the following configuration:

 
{noformat}
<connectors>
    <connector name="artemis-primary">tcp://primaryA:61616</connector>
    <connector name="artemis-backup">tcp://backupB:61616</connector>
</connectors>

<acceptors>
    <acceptor name="artemis">tcp://0.0.0.0:61616?tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;amqpMinLargeMessageSize=102400;protocols=CORE,AMQP,STOMP,HORNETQ,MQTT,OPENWIRE;useEpoll=true;amqpCredits=1000;amqpLowCredits=300;amqpDuplicateDetection=true;supportAdvisory=false;suppressInternalManagementObjects=false</acceptor>
    <acceptor name="amqp">tcp://0.0.0.0:5672?tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;protocols=AMQP;useEpoll=true;amqpCredits=1000;amqpLowCredits=300;amqpMinLargeMessageSize=102400;amqpDuplicateDetection=true</acceptor>
</acceptors>{noformat}
 

Port 5672 is exposed for AMQP clients. Port 61616 is used just to form a cluster. For security reasons, to disable Core availability, it is unavailable to the clients.

In standard AMQP 1.0 client, for example in Qpid JMS client, we want to use both servers, so we specify the following connection URL:

 
{noformat}
failover:(amqp://primaryA:5672,amqp://backupB:5672){noformat}
Under normal circumstances this works, but if broker failover is performed, or if one kills network reachability of the primary node, AMQP  client then tries to connect to amqp://backupB:616161 instead of port 5672. That hostname comes as a part of AMQP “open” frame during initial connection to the primary broker, which then replaces client’s connection URL.

 

As a workaround we have `failover.amqpOpenServerListAction=IGNORE` transport option. However, it is not always possible to apply this property for all clients. For example, in case clients are external, not under the control of broker party.

It would be great to have a possibility to somehow manually specify topology hostname list from the side of the broker. This is potentially useful for other cases too, where acceptor port or hostname is different from connector port/hostname:
 # Clients connect through SSL, but cluster connector topology don't need SSL.
 # Clients connect through load balancer and external DNS is used, but the same load balancer cannot be used internally and cluster connectors rely on internal DNS.

Maybe even expand this to other wire protocols, which support dynamic topology changes.

 



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

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@artemis.apache.org
For additional commands, e-mail: issues-help@artemis.apache.org