"Deprecated features are being used" for transient_nonexcl_queues even when there are no transient queues in the cluster

[daanwa]

Describe the bug

After a clean install of RabbitMQ 4.0.4 and configuring deprecated_features.permit.transient_nonexcl_queues = false in /etc/rabbitmq/rabbitmq.conf, creating a queue via the RabbitMQ Management Interface, I get the message "Deprecated features are being used".

If I look in "Admin -> Deprecated features" I see that transient_nonexcl_queues is "in_use". This also occurs when I use a stream queue or quorum queue.

I would expect this message to not show when I create a new queue (of any type).

Perhaps I'm misunderstanding how these feature flags work. But I would expect this feature to not be enabled (?) or usable upon a fresh install of RabbitMQ 4.0.4

Reproduction steps

1. Install RabbitMQ
2. Add deprecated_features.permit.transient_nonexcl_queues = false to the config file
3. Restart RabbitMQ
4. Create a queue of any type
5. See the message
6. See that transient_nonexcl_queues is "in_use"

Expected behavior

To not have transient_nonexcl_queues is "in_use" when creating a new queue in a fresh RabbitMQ 4.0.4 install

Additional context

No response

[Dutchy-]

I just upgraded to 4.0.4 and I also get this message. I do not have transient_nonexcl_queues explicitly disabled but I cannot find any queue that uses it. I only have quorum queues.

[michaelklishin]

Yes, the function that detects if transient non-exclusive queues are used does not do it correctly at least with Mnesia.

This was the conclusion of #12793.

This is a harmless warning, although I understand that it is annoying.

[Tazmaniac]

All my classic queues are either "exclusive: true" or "auto-delete:true x-expires:10000" but after the upgrade to from 4.0.4 to 4.0.5 of my cluster, I still have the deprecated feature message in the interface.
Is it because I did not completely shutdown the cluster ?
Are "auto-delete:true x-expires:10000" classic queues considered "transient_nonexcl_queues" queues ? In this case which alternatives I have ?
Or is the fix incomplete ?

[mkuratczyk]

I've checked and I don't see an error here. I guess your "auto-delete:true x-expires:10000" are non-durable (in other words: transient) and that's what triggers the warning.

[michaelklishin]

@Tazmaniac this is not a support forum. Discussions are.

You must restart cluster nodes in case of an upgrade, and if some nodes are not upgraded, certain behaviors of earlier versions are to be expected.

Neither TTL nor auto-deletion is at play in transient_nonexcl_queues. The rule only takes into account non-durable (transient) and non-exclusive queues. Their TTL and auto-deletion settings are not considered.

I have not seen any false positives since #12840.