[Questions] [No details to work with] quorum queue consumer cannot be recovered

[dormanze]

Community Support Policy

• I have read RabbitMQ's Community Support Policy
• I agree to provide all relevant information (versions, logs, rabbitmq-diagnostics output, detailed reproduction steps)

RabbitMQ version used

3.13.6

Erlang version used

26.2.x

Operating system (distribution) used

linux

How is RabbitMQ deployed?

Generic binary package

rabbitmq-diagnostics status output

See https://www.rabbitmq.com/docs/cli to learn how to use rabbitmq-diagnostics

Logs from node 1 (with sensitive values edited out)

See https://www.rabbitmq.com/docs/logging to learn how to collect logs

# PASTE LOG HERE, BETWEEN BACKTICKS

Logs from node 2 (if applicable, with sensitive values edited out)

See https://www.rabbitmq.com/docs/logging to learn how to collect logs

# PASTE LOG HERE, BETWEEN BACKTICKS

Logs from node 3 (if applicable, with sensitive values edited out)

See https://www.rabbitmq.com/docs/logging to learn how to collect logs

# PASTE LOG HERE, BETWEEN BACKTICKS

rabbitmq.conf

See https://www.rabbitmq.com/docs/configure#config-location to learn how to find rabbitmq.conf file location

# PASTE rabbitmq.conf HERE, BETWEEN BACKTICKS

Steps to deploy RabbitMQ cluster

RabbitMQ cluster with three nodes.

Steps to reproduce the behavior in question

After the data disk permission of one RabbitMQ is changed to 000, RabbitMQ crashes and consumers in the arbitration queue do not automatically recover.
chmod 000 -R /opt/rabbitmq/data

advanced.config

See https://www.rabbitmq.com/docs/configure#config-location to learn how to find advanced.config file location

# PASTE advanced.config HERE, BETWEEN BACKTICKS

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?

We use the Java client, where the automatic recovery of the client is disabled, and we actively listen to the connection and channel shutdown events. When an exception is triggered, the server crashes occasionally and does not notify the client of the shutdown event. As a result, the client does not recover automatically. I added some logs to the server, and the consumer was always deleted by a strange channel, which was not the channel that created the consumer.

[michaelklishin]

@dormanze look at you, first ticked the box saying that you will provide all relevant information and ended up providing next to nothing relevant. Do you think we are asking for those logs for the kicks of it? Should on top of that we guess what does "server crashes" means, e.g. what exception the node logs?

In any case, 3.13 is out of community support. Try against against 4.0.3 and provide all logs and more detailed descriptions this time around.