Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
druminski opened this issue Dec 5, 2016 · 0 comments
Labels

Comments

@druminski
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant