[ARTEMIS-2972] Client Load-Balancing strategies

• Type: New Feature
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Component/s: API
• Assignee: Unassigned
• Reporter: Apache Dev
• Created: 01/Nov/20 18:26
• Updated: 26/Oct/21 15:58
• Resolved: 26/Oct/21 15:58

Description

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.

Issue Links

• is fixed by: ARTEMIS-3365 Broker Balancers