activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jiri Danek (JIRA)" <j...@apache.org>
Subject [jira] [Issue Comment Deleted] (ARTEMIS-921) Consumers killed as slow even if overall consuming rate is above threshold
Date Mon, 16 Jan 2017 16:35:26 GMT

     [ https://issues.apache.org/jira/browse/ARTEMIS-921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jiri Danek updated ARTEMIS-921:
-------------------------------
    Comment: was deleted

(was: [slightly OT], looking at the code, does this Slow Consumers feature play well with
the Message Selectors feature? What if producer sends messages with {myProperty='a'} and consumer
consumes only {myProperty='b'}. Will the consumer be killed as slow?)

> Consumers killed as slow even if overall consuming rate is above threshold
> --------------------------------------------------------------------------
>
>                 Key: ARTEMIS-921
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-921
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 1.5.1
>            Reporter: Howard Gao
>            Assignee: Howard Gao
>             Fix For: 1.5.next
>
>
> 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
(v6.3.4#6332)

Mime
View raw message