[ARTEMIS-5042] The load balancing is not working correctly when several brokers are down

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.35.0
• Fix Version/s: 2.38.0
• Component/s: Balancer

Environment

Cluster Configuration broker.xml:

 
<cluster-connections>
         <cluster-connection name="mccon">
        <connection-ttl>60000</connection-ttl>
            <call-timeout>5000</call-timeout>
            <retry-interval>500</retry-interval>
            <retry-interval-multiplier>1.0</retry-interval-multiplier>
            <max-retry-interval>5000</max-retry-interval>
            <initial-connect-attempts>-1</initial-connect-attempts>
            <reconnect-attempts>-1</reconnect-attempts>
    <forward-when-no-consumers>false</forward-when-no-consumers>    
            <connector-ref>artemis</connector-ref>
            <message-load-balancing>ON_DEMAND</message-load-balancing>
            <max-hops>1</max-hops>
            <static-connectors>
               <connector-ref>node0</connector-ref>
               <connector-ref>node1</connector-ref>
               <connector-ref>node2</connector-ref>
 
            </static-connectors>
         </cluster-connection>
      </cluster-connections>

• Assignee: Justin Bertram
• Reporter: jjmarin
• Created: 10/Sep/24 09:45
• Updated: 16/Oct/24 16:02
• Resolved: 16/Oct/24 15:59

Description

The load balancing is not working correctly when several brokers are down. With the configuration we have in the cluster, we understand that this should not be happening. The load balancing should be smart and not send messages to the nodes that are down."

Issue Links

• links to: GitHub Pull Request #5246