You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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
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.
The text was updated successfully, but these errors were encountered:
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
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
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.
The text was updated successfully, but these errors were encountered: