-
Notifications
You must be signed in to change notification settings - Fork 191
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
Consumer gets stuck on ack #608
Comments
Update: The issue only occurs in a docker swarm cluster. Using a normal docker or a normal rabbitmq instance works fine. |
Hey @kimdre did you notice if messages would start build up after consumer(s) stuck? Also, if there is a specific message size limit at which point the issue persistently occurs? |
Hi, yes the publisherstill worked so new messages were building up in the queue while the consumers didn't do anything despite being connected. |
I've seen something similar that was caused by MTU size mismatch along the networking route so once a message that was larger than 8500 bytes arrives RabbitMQ connection gets stuck forever. The solution was to configure proper peering connection as it was purely an infrastructure thing (AWS). This docs from AWS describes well what was happening: https://docs.aws.amazon.com/vpc/latest/tgw/transit-gateway-quotas.html#mtu-quotas
|
I'm trying to run a consumer in a docker swarm cluster.
The app consumes multiple events from a queue, writes them as bulk a database and then afterwards acknowledges them all.
For some reason, however, the consumer often gets stuck when acknowledging the messages while the connection stays open, especially when the app consumes a lot of messages at once and also consumes far less than it could.
A simple restart to fix the consumer also doesn't work, as it still won't consume any messages anymore (except for 1 to 4 messages, then it gets stuck again).
To fix it, I have to first delete the queue with all messages in it and then I can restart the consumer app.
When I try to run this exact setup in a normal docker stack on my computer without swarm enabled, it works fine for some reason.
The code looks like this:
The text was updated successfully, but these errors were encountered: