RabbitMQ Khepri / Quorum Queue Channels Stuck in suspected_down Status

Products

• VMware Tanzu Data Suite
• RabbitMQ
• VMware Tanzu RabbitMQ

Issue/Introduction

In RabbitMQ 4.1.4 with Khepri enabled and quorum queues in use, channels can become stuck in suspected_down. The TCP connection remains open, the channel is not closed, and client operations may hang without a client-side error.

Environment

• RabbitMQ 4.1.4.
• Khepri metadata store enabled.
• Quorum queues in use.

Cause

This is a known RabbitMQ 4.1.4 product issue involving channel state tracking in the khepri-enabled environments. The affected channel may remain stuck even though the connection is still alive.

Resolution

Upgrade to RabbitMQ 4.1.10 or later or RabbitMQ 4.2.5 or later.

Additional Information

References

 

• RabbitMQ Khepri failure recovery guidance
• RabbitMQ quorum queue status monitoring guidance
• RabbitMQ Release-notes
• RabbitMQ Known Issues with Khepri