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
{{ message }}
This repository has been archived by the owner on Oct 30, 2020. It is now read-only.
guv does not know the identity of messages nor their contents (nor should it).
So to monitor whether jobs are being processed in an orderly fashion, we'd have to look at the ACK ratio - which I think RabbitMQ provides. And then compare it to the theoretical throughput (which we have an estimate for). If this is way off, say 5-10 times too low, we could then ask Heroku to restart the role/dyno-type.
There are however, no guarantees that this will clear the problem. But it may in some cases.
This is not a condition which should occur, so it should also be reported as an error.
Guv could be useful for detecting, and potentially remedying queues that are deadlocked and not moving
The text was updated successfully, but these errors were encountered: