You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@activemq.apache.org by "Gary Tully (Jira)" <ji...@apache.org> on 2021/01/27 14:00:11 UTC

[jira] [Updated] (ARTEMIS-3064) Disable useTopologyForLoadBalancing for non HA federation connections between clusters

     [ https://issues.apache.org/jira/browse/ARTEMIS-3064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Tully updated ARTEMIS-3064:
--------------------------------
    Summary: Disable useTopologyForLoadBalancing for non HA federation connections between clusters  (was: Enable/Disable useTopologyForLoadBalancing for federation connections between clusters)

> Disable useTopologyForLoadBalancing for non HA federation connections between clusters
> --------------------------------------------------------------------------------------
>
>                 Key: ARTEMIS-3064
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-3064
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>          Components: Federation
>    Affects Versions: 2.16.0
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>            Priority: Major
>             Fix For: 2.17.0
>
>          Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> The core client respects the topology for loadbalancing by default. A federation connection configures and reuses a server locator via it's circuit breaker.
> With ha = false, it looks like we should disable useTopologyForLoadBalancing such that the circuit reconnect gets back to the original broker even when clustered.
> With ha=true, the reconnect can be to any broker in the cluster in the normal way.



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