Skip to content

Reading rate should not depend on successes and failures of sending messages #656

@druminski

Description

@druminski

We have a subscription which filters 1k msgs/s and sends only ~1 msg/s.

Recently this subscription encountered on a timeout and its output rate was decreased from 5k msgs/s to 1 msg/s because of small amount of delivery rate. Below chart visualises this situation

screen shot 2016-12-05 at 11 38 02

Unfortunately when output rate was decreased then reading/filtering messages from this subscription also decreased to 1 msgs/s and we immediately received lag. Here we can see that filtering on subscription was stopped

screen shot 2016-12-05 at 12 45 05

After that output rate didn't increase because reading was so slow that there were no "good" messages in that time. That kind of situations require manual intervention and consumer restart.
Maybe reading rate should not depend on output rate.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions