Replies: 1 comment 1 reply
-
The exception means that a quorum queue replica times out registering a consumer. There are no details as to why that might be, the queue can have an online minority at that time. Unless there is a way to reproduce against |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Community Support Policy
RabbitMQ version used
3.13.7 or older
Erlang version used
26.2.x
Operating system (distribution) used
Ubuntu 22.04.5 LTS
How is RabbitMQ deployed?
Debian package
rabbitmq-diagnostics status output
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.conf
Steps to deploy RabbitMQ cluster
RabbitMQ Official Doc steps to install RabbitMQ on Ubuntu machines
Steps to reproduce the behavior in question
When the NiFi consumers were stopped due to [XYZ reason] and all the messages were in a ready state, once the consumers resumed and started consuming a large number of messages (around 3.5 million), I started seeing errors in the logs and was unable to consume any messages from the RMQ nodes
advanced.config
See 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
What problem are you trying to solve?
To able to consume messages that are in Ready State on RabbitMQ Cluster
Beta Was this translation helpful? Give feedback.
All reactions