[
https://issues.apache.org/jira/browse/ARTEMIS-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16500816#comment-16500816
]
ASF subversion and git services commented on ARTEMIS-1902:
----------------------------------------------------------
Commit db973cc2616749310be3dc21211d438b927e96fe in activemq-artemis's branch
refs/heads/2.6.x from [~jbertram]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=db973cc ]
ARTEMIS-1902 decrement before returning
(cherry picked from commit be36d3078ceafe3df06a1686426f5d948dfadc2c)
> Message redistribution is not stopped when consumers count on remote node
> reaches 0 (AMQP)
> ------------------------------------------------------------------------------------------
>
> Key: ARTEMIS-1902
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1902
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 2.5.0, 2.6.0
> Reporter: Martyn Taylor
> Assignee: Martyn Taylor
> Priority: Critical
> Fix For: 2.6.1, 2.7.0
>
>
> With redistribution enabled and load balancing set to ON_DEMAND there is a
> case where a consumer count on a remote node reaches 0, however the local
> broker continues redistributing. This can cause a whole magnitude of issues
> if the both brokers get in the same state. Messages are redistributed back
> and forth between each other and never hit the local queue, resulting in
> message loss and potentially an OOM as each time the message is redistributed
> a copy is made.
> The issue looks to be caused by the cluster getting into a state where
> consumer counts are below 0.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)