Uploaded image for project: 'AMQ Broker'
  1. AMQ Broker
  2. ENTMQBR-2386

Slow consumers not disconnected if producer msg/s rate is low

    XMLWordPrintable

Details

    • 3
    • Release Notes
    • Hide
      Previously, when checking for slow consumers, the broker calculated only messages added by a producer during the check period. The broker did not take into account existing messages in the queue at the start of the check period. This could cause the broker to miss legitimate cases of slow message consumption. This situation could arise, for example, if a producer previously sent large numbers of messages to the queue in bursts, but was idle during the slow consumer check period. This issue is now resolved.
      Show
      Previously, when checking for slow consumers, the broker calculated only messages added by a producer during the check period. The broker did not take into account existing messages in the queue at the start of the check period. This could cause the broker to miss legitimate cases of slow message consumption. This situation could arise, for example, if a producer previously sent large numbers of messages to the queue in bursts, but was idle during the slow consumer check period. This issue is now resolved.
    • Documented as Resolved Issue
    • ARTEMIS-1011
    • Verified in a release
    • AMQ Broker 2019, AMQ Broker 2319

    Description

      There is still a problem how producer msg/s rate is calculated in QueueImpl.getRate() for slow consumer detection. It calculates only messages added during the last slow consumer check period. As this is used to figure out, in which msg/s rate the queue could serve the consumer then it should also take into account messages which are already in queue at the start of queueRateCheckTime period.

      Current implementation is problem for cases when messages are sent to queue in bursts, for example producer sends 1000s messages in a few seconds and then stops and will do that again in 1 hour. QueueImpl.getRate() method returns 0 msg/s for slow consumer check period set to for example 5 min and slow consumer detection will be skipped.

      Attachments

        Issue Links

          Activity

            People

              dbruscin Domenico Francesco Bruscino
              ehugonne1@redhat.com Emmanuel Hugonnet
              Michal Toth Michal Toth
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: