[Questions] some producer connect to RabbitMQ timed out #14447
-
Community Support Policy
RabbitMQ version used4.0.6 Erlang version used26.2.x Operating system (distribution) usedlinux How is RabbitMQ deployed?Generic binary package rabbitmq-diagnostics status outputSee https://www.rabbitmq.com/docs/cli to learn how to use rabbitmq-diagnostics
Logs from node 1 (with sensitive values edited out)![]() Logs from node 2 (if applicable, with sensitive values edited out)See https://www.rabbitmq.com/docs/logging to learn how to collect logs
Logs from node 3 (if applicable, with sensitive values edited out)See https://www.rabbitmq.com/docs/logging to learn how to collect logs
rabbitmq.confSee https://www.rabbitmq.com/docs/configure#config-location to learn how to find rabbitmq.conf file location
Steps to deploy RabbitMQ clusterconfig and run rabbitmq Steps to reproduce the behavior in questionproducters and consumers restart advanced.configSee https://www.rabbitmq.com/docs/configure#config-location to learn how to find advanced.config file location
Application code# PASTE CODE HERE, BETWEEN BACKTICKS Kubernetes deployment file# Relevant parts of K8S deployment that demonstrate how RabbitMQ is deployed
# PASTE YAML HERE, BETWEEN BACKTICKS What problem are you trying to solve?some producer connect to RabbitMQ timed out
rabbitmq server print some notice message |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
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. |
Beta Was this translation helpful? Give feedback.
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.