activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (ARTEMIS-921) Consumers killed as slow even if overall consuming rate is above threshold
Date Tue, 17 Jan 2017 01:50:26 GMT


ASF GitHub Bot commented on ARTEMIS-921:

Github user gaohoward commented on a diff in the pull request:
    --- Diff: artemis-server/src/main/java/org/apache/activemq/artemis/core/server/impl/
    @@ -3159,6 +3162,9 @@ public void run() {
    +                        //break once a consumer gets killed. This can prevent all
    +                        //consumers to this queue get killed all at once.
    +                        break;
    --- End diff --
    @clebertsuconic Thanks!

> Consumers killed as slow even if overall consuming rate is above threshold
> --------------------------------------------------------------------------
>                 Key: ARTEMIS-921
>                 URL:
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 1.5.1
>            Reporter: Howard Gao
>            Assignee: clebert suconic
>             Fix For: 1.5.2, 2.0.0
> We have one queue. Imagine messages are produced at 2 msgs/s. There are three consumers
and slow consumer limit is 1 msgs/s. What happens is that all three consumers get killed as
slow, even though it is impossible for any of them to be fast, since messages are distributed
equally between the consumers (round-robin).
> This has real consumer impact in a situation when producer rate is usually high (so it
requires multiple consumers working in parallel), but may occasionally drop close to consumer-threshold.
In this case, broker disconnects all consumers who then have to reconnect and message processing
is delayed for the time of the reconnecting.

This message was sent by Atlassian JIRA

View raw message