Skip to content
This repository has been archived by the owner on Oct 30, 2020. It is now read-only.

Detect stuck queues #62

Open
bergie opened this issue Dec 10, 2015 · 2 comments
Open

Detect stuck queues #62

bergie opened this issue Dec 10, 2015 · 2 comments
Milestone

Comments

@bergie
Copy link
Member

bergie commented Dec 10, 2015

Guv could be useful for detecting, and potentially remedying queues that are deadlocked and not moving

@jonnor
Copy link
Member

jonnor commented Dec 28, 2015

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.

@bergie
Copy link
Member Author

bergie commented Dec 28, 2015

Yeah, I think just detecting it and reporting an error would be a good start here

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

No branches or pull requests

2 participants