[
https://issues.apache.org/jira/browse/ARTEMIS-2972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram resolved ARTEMIS-2972.
-------------------------------------
Resolution: Fixed
Check out ARTEMIS-3365. I believe it would help with your use-case.
> Client Load-Balancing strategies
> --------------------------------
>
> Key: ARTEMIS-2972
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2972
> Project: ActiveMQ Artemis
> Issue Type: New Feature
> Components: API
> Reporter: Apache Dev
> Priority: Minor
>
> New brokers joining a cluster could remain underutilized, unless existing
> clients create new connections to them.
> When a new broker is started and joins the existing cluster, existing clients
> can be notified using {{ClusterTopologyListener}}.
> Such clients can create new connections with {{ServerLocator}}, using its own
> load-balancing mechanism or targeting "manually" a specific broker.
> {{ConnectionLoadBalancingPolicy}} can be used to choose the strategy for
> {{ServerLocator}} to create a new connection.
> However, no informations are provided to the policy implementor about brokers
> to choose.
> In highly dynamic scenarios (say that there are multiple clients and many
> brokers can go up and down), it would be necessary to keep in sync with
> topology updates and create new connections manually. It could be challenging
> to grant that one and only one connection is created to each broker.
> In such a situation, clients should be made even more agnostic about
> clustering, and should automatically leverage brokers joining the cluster.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
