[jira] [Commented] (ARTEMIS-921) Consumers killed as slow even if overall consuming rate is above threshold

["Howard Gao (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ARTEMIS-921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15823677#comment-15823677 ] 

Howard Gao commented on ARTEMIS-921:
------------------------------------

The solution could be not to kill all consumers all at once. If during one check a consumer is killed, then don't check the others this time, leave it to next check. This will give the other consumers a chance to calculate the updated rate (once a consumer is killed, the message consuming rate for the rest of consumers will increase afterwards).



> 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)