[
https://issues.apache.org/jira/browse/ARTEMIS-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16500784#comment-16500784
]
ASF GitHub Bot commented on ARTEMIS-1902:
-----------------------------------------
GitHub user jbertram opened a pull request:
https://github.com/apache/activemq-artemis/pull/2121
ARTEMIS-1902 decrement before returning
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jbertram/activemq-artemis ARTEMIS-1902
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq-artemis/pull/2121.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2121
----
commit be36d3078ceafe3df06a1686426f5d948dfadc2c
Author: Justin Bertram <jbertram@...>
Date: 2018-06-04T20:01:04Z
ARTEMIS-1902 decrement before returning
----
> 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)
