Skip to content
Discussion options

You must be logged in to vote

The log messages mean that a resource (memory) alarm has gone into effect and then was cleared in a few seconds, several times. There is a doc guide for that.

The timeout in question was a channel opening timeout, which is expected on a connection that was blocked by a resource alarm (that means it has published at least one messages after the alarm has gone into effect) because RabbitMQ stops reading from the socket when a connection blocked due to a resource alarm.

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@lukebakken
Comment options

Answer selected by michaelklishin
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
3 participants