"rabbitmqadmin get" behavior with ackmode set to ack_requeue_true

[zhuleiandy888]

Describe the bug

OS and Images:

k8s node os: CentOS 7.9
container image: rabbitmq:4.0.9-management

Detailed command parameters:

rabbitmqadmin get: ackmode default value : 'ackmode': 'ack_requeue_true'

Output of execution process results:

root@rabbitmq-0:/# rabbitmqadmin -uadmin -padmin123 list queues test001  messages
+---------+----------+
| test001 | messages |
+---------+----------+
|         | 5        |
+---------+----------+
root@rabbitmq-0:/# rabbitmqadmin -uadmin -padmin123 get queue=test001 count=8
+-------------+------------+---------------+--------------------------+---------------+------------------+------------+-------------+
| routing_key |  exchange  | message_count |         payload          | payload_bytes | payload_encoding | properties | redelivered |
+-------------+------------+---------------+--------------------------+---------------+------------------+------------+-------------+
| test001     | test001-ex | 4             | hi, this is frist seven! | 24            | string           |            | True        |
| test001     | test001-ex | 3             | hi, this is frist eight! | 24            | string           |            | True        |
| test001     | test001-ex | 2             | hi, this is frist five!  | 23            | string           |            | True        |
| test001     | test001-ex | 1             | hi, this is frist six!   | 22            | string           |            | True        |
| test001     | test001-ex | 0             | hi, this is frist eight! | 24            | string           |            | False       |
+-------------+------------+---------------+--------------------------+---------------+------------------+------------+-------------+
root@rabbitmq-0:/# rabbitmqadmin -uadmin -padmin123 get queue=test001 count=9
+-------------+------------+---------------+--------------------------+---------------+------------------+-------------+
| routing_key |  exchange  | message_count |         payload          | payload_bytes | payload_encoding | redelivered |
+-------------+------------+---------------+--------------------------+---------------+------------------+-------------+
| test001     | test001-ex | 3             | hi, this is frist seven! | 24            | string           | True        |
| test001     | test001-ex | 2             | hi, this is frist eight! | 24            | string           | True        |
| test001     | test001-ex | 1             | hi, this is frist six!   | 22            | string           | True        |
| test001     | test001-ex | 0             | hi, this is frist eight! | 24            | string           | True        |
+-------------+------------+---------------+--------------------------+---------------+------------------+-------------+
root@rabbitmq-0:/# rabbitmqadmin -uadmin -padmin123 get queue=test001 count=9
+-------------+------------+---------------+--------------------------+---------------+------------------+-------------+
| routing_key |  exchange  | message_count |         payload          | payload_bytes | payload_encoding | redelivered |
+-------------+------------+---------------+--------------------------+---------------+------------------+-------------+
| test001     | test001-ex | 2             | hi, this is frist seven! | 24            | string           | True        |
| test001     | test001-ex | 1             | hi, this is frist eight! | 24            | string           | True        |
| test001     | test001-ex | 0             | hi, this is frist eight! | 24            | string           | True        |
+-------------+------------+---------------+--------------------------+---------------+------------------+-------------+
root@rabbitmq-0:/# rabbitmqadmin -uadmin -padmin123 get queue=test001 count=1
+-------------+------------+---------------+--------------------------+---------------+------------------+-------------+
| routing_key |  exchange  | message_count |         payload          | payload_bytes | payload_encoding | redelivered |
+-------------+------------+---------------+--------------------------+---------------+------------------+-------------+
| test001     | test001-ex | 2             | hi, this is frist seven! | 24            | string           | True        |
+-------------+------------+---------------+--------------------------+---------------+------------------+-------------+
root@rabbitmq-0:/# rabbitmqadmin -uadmin -padmin123 get queue=test001 
+-------------+------------+---------------+--------------------------+---------------+------------------+-------------+
| routing_key |  exchange  | message_count |         payload          | payload_bytes | payload_encoding | redelivered |
+-------------+------------+---------------+--------------------------+---------------+------------------+-------------+
| test001     | test001-ex | 2             | hi, this is frist eight! | 24            | string           | True        |
+-------------+------------+---------------+--------------------------+---------------+------------------+-------------+
root@rabbitmq-0:/# rabbitmqadmin -uadmin -padmin123 list queues test001  messages
+---------+----------+
| test001 | messages |
+---------+----------+
|         | 3        |
+---------+----------+
root@rabbitmq-0:/# rabbitmqadmin -uadmin -padmin123 list queues test001  messages
+---------+----------+
| test001 | messages |
+---------+----------+
|         | 3        |
+---------+----------+
root@rabbitmq-0:/# rabbitmqadmin -uadmin -padmin123 list queues test001  messages
+---------+----------+
| test001 | messages |
+---------+----------+
|         | 3        |
+---------+----------+
root@rabbitmq-0:/# rabbitmqadmin -uadmin -padmin123 list queues test001  messages
+---------+----------+
| test001 | messages |
+---------+----------+
|         | 3        |
+---------+----------+

Reproduction steps

...

Expected behavior

none

Additional context

none

[mkuratczyk]

Is this a quorum queue? If yes, you are probably reaching the delivery-limit: https://www.rabbitmq.com/docs/quorum-queues#poison-message-handling

If that's not what it is, please provide full reproduction steps, starting from declaring the queue and publishing to it

[michaelklishin]

@zhuleiandy888 rabbitmqadmin get and its underlying polling consumer mechanism, basic.get, are both explicitly recommended against in the docs.

That operation/command technically can use manual acknowledgements and there is a management UI option for that but it's a weird combination that almost no one uses.

So very likely you consume messages from your queues in automatic acknowledgement mode, which schedules them for removal immediately (as soon as RabbitMQ writes a polled messages to the client socket), and nothing is "lost".

RabbitMQ 4.0.x is out of community support. We need a way to reproduce against 4.2.0 or 4.1.x but better yet, consider not using rabbitmqadmin get at all, for anything, and use a regula consumer instead.

Right now we do not even know what version of rabbitmqadmin is used. rabbitmqadmin v1 in Pytnon won't get any more updates. rabbitmqadmin v2 is the only version under development and it explicitly recommends against rabbitmqadmin get.