4.1.x: channels, sessions that consume from quorum queues can leak Raft segment file handles

[michaelklishin]

Describe the bug

I'm filing this for visibility.

This should be addressed by #14127.

#14143 is also somewhat relevant.

Reproduction steps

1. Upgrade to a 4.1.x version up to 4.1.1
2. Declare a quorum queue
3. Start a client that would consume from said quorum queue
4. Add meaningful load (say, a few thousands of messages per second) to that queue so that it uses multiple segment files
5. Add more consuming channels
6. Delete the queue but keep the channels around

Expected behavior

The file handles opened by the consuming channels/sessions are closed.

Additional context

No response

[stephen841526]

hello.
we are running our solution on RabbitMQ and recently upgraded from version 3.10.7 to 4.1.1,
After the upgrade, we encountered an issue where file descriptors kept increasing , our service processes became unresponsive , and the number of ready message in the queues grew fastly.
Could you confirm if this issue is the one that was fixed in RabbitMQ 4.1.3, as mentioned in the release notes?

Thank you in advance.

[mkuratczyk]

@stephen841526 could you confirm that? upgrade to the latest patch release (a good idea anyway) and report whether the problem persist. We don't know if you've hit exactly this issue. Likely yes, but perhaps there's a different one, that we are not aware of.

[michaelklishin]

@stephen841526 we are engineers, not magicians. We won't guess what exactly happened in your system.

FWIW this addresses the only known issue that would have "the number of file descriptors keeps growing more or less monotonically" in 4.1.x, and it was discovered specifically using 4.1.1.

The most recent RabbitMQ release is 4.1.4.