-
Notifications
You must be signed in to change notification settings - Fork 9
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
RabbitMQ service stopped consuming, but remained "healthy" #490
Labels
bug
Something isn't working
Comments
We had the same problem. Our service was unable to publish messages but the healthcheck stayed healthy. In our case the service was printing a lot of errors:
and we had a second exception later due to a memory leak:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We ran into a case tonight where one of our RabbitMQ services stopped consuming messages without logging any error. This resulted in the queue filling up gradually until we manually restarted the pods from the service which fixed the problem.
Unfortunately, the
MessageProcessingHealthCheck
did not help here which was supposed to prevent situations like this because it's only checking whether elements are in the internal queue without anything being processed, but the service did not consume messages from its queue any more so the internal queue stayed completely empty.It was by the way quite easy to inspect the problem thus far thanks to the Motor.NET and RabbitMQ metrics which is nice 😃
But we don't know yet why the consumer apparently stopped working.
For reference, we're using Motor.NET 0.9.10.
The text was updated successfully, but these errors were encountered: