[
https://issues.apache.org/jira/browse/ARTEMIS-3064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17270093#comment-17270093
]
Gary Tully commented on ARTEMIS-3064:
-------------------------------------
i have researched this a bit, seems the norm is to put this locator config in
the url as query parameters, however with a connector-ref, there can be many
urls and the server locator is shared, the locator config would need to be
duplicated. Some of the locator properties are explicitly exposed and I think
it makes sense to reduce the options in the context of federation b/c there is
a circuit breaker doing the reconnect logic. combining this with ha = false
seems sensible.
> Enable/Disable useTopologyForLoadBalancing for 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
>
>
> 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)
