Connection Churn in RabbitMQ with Kombu 5.5.0 #2273
Description
Hello,
We're observing an issue we believe was introduced with Kombu 5.5.0 manifesting as connection/channel churn in RabbitMQ.
Environment:
Kombu version: 5.5.0
Broker: RabbitMQ 3.12.7
Observed in a Celery context (but likely stems from Kombu layer)
Description:
After upgrading to Kombu 5.5.0, RabbitMQ logs and management UI show vastly increased connection/channel create and delete activity.
Pinning to Kombu 5.4.2 eliminates the excessive churn, suggesting a regression or unintended side effect in 5.5.0.
The recently published 5.5.1 has not yet been tested.
This behavior leads to:
Unnecessary load on the broker
Excessive logging
Potential side effects for monitoring or scaling tools that track queue/binding activity
I'm happy to include more details as requested, just wanted to get the issue started/logged.