[
https://issues.apache.org/jira/browse/ARTEMIS-5042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17880682#comment-17880682
]
Justin Bertram commented on ARTEMIS-5042:
-----------------------------------------
bq. The node or nodes that remain alive will not detect if another node comes
back up again.
That is incorrect.
If the node that stopped is restarted *before* the other nodes have given up
trying to reconnect then the other nodes will reconnect and the messages in the
store-and-forward queues will be distributed to the restarted node as if
nothing happened.
If the node that stopped is restarted *after* the other nodes have given up
trying to reconnect then the store-and-forward queues on the other nodes will
have been cleaned up and all the messages in them will have been put into their
corresponding local queues. However, the restarted node will send a "node
announce" message to the other nodes in the cluster and they will all establish
new cluster-connections to the restarted node (and create the requisite
internal store-and-forward queues, etc.).
bq. The node which has back up alive, will always remain as down for the rest
of the nodes that are still up.
That is incorrect. See the previous answer for details.
bq. This gonna work like this until the nodes that were up, get restarted.
That is incorrect. See the previous answer for details.
> The load balancing is not working correctly when several brokers are down
> -------------------------------------------------------------------------
>
> Key: ARTEMIS-5042
> URL: https://issues.apache.org/jira/browse/ARTEMIS-5042
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Balancer
> Affects Versions: 2.35.0
> 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>
> Reporter: Juanjo Marin
> Assignee: Justin Bertram
> Priority: Major
> Attachments: 1NodoUp.PNG, 3Nodosup.PNG,
> QueueInternWithMessageNoConsumer.PNG
>
>
> 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."
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
