consumer-timeout not working. What am I doing wrong?

[Josh Holdaway]

Hello,

I've modified the c# tutorial sample to include the following:

channel.QueueDeclare(queue: "task_queue",
 durable: true,
 exclusive: false,
 autoDelete: false,
 arguments: new Dictionary<string, object>() { { "x-consumer-timeout", 10000 } });

Notice I added the x-consumer-timeout.  It seems to be not doing anything?  I'm expecting after 10 seconds if I don't acknowledge, it would give the message to another consumer.

What am I doing wrong?

[Michal Kuratczyk]

It was added in 3.11.15, just 2 weeks ago. Are you running the latest version?

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-user...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/rabbitmq-users/6d2c6595-edfa-4b17-84da-7e31c819aab3n%40googlegroups.com.

--

Michał

RabbitMQ team

[Josh Holdaway]

Is this correct in the docker compose?

  rabbit:
    image: "rabbitmq:3-management"

[Michal Kuratczyk]

Yes, if you actually pull it. If you pulled from this tag before, you may be using a cached image. 

To view this discussion on the web, visit https://groups.google.com/d/msgid/rabbitmq-users/b0c13dc1-cd40-4c4c-bab5-0075843f4209n%40googlegroups.com.

--

Michał

[Josh Holdaway]

It says 3.11.15 in the management console.

[Michal Kuratczyk]

Well, maybe there's a bug or misunderstanding in how it works. Please provide a test case - a script or a series of commands we can run to see the problem.

Best,

To view this discussion on the web, visit https://groups.google.com/d/msgid/rabbitmq-users/72a063ef-84ed-43eb-b97d-16e47c222cfdn%40googlegroups.com.

--

Michał

RabbitMQ team

[Josh Holdaway]

Hello,

I've just modified the sample code here: https://www.rabbitmq.com/tutorials/tutorial-two-dotnet.html

I just changed the code for the queuedeclare to include the arguement:

channel.QueueDeclare(queue: "task_queue",
 durable: true,
 exclusive: false,
 autoDelete: false,
 arguments: new Dictionary<string, object>() { { "x-consumer-timeout", 10000 } });

In the worker I changed the Thread.Sleep to Thread.Sleep(20000);

To test, I start 2 workers up, and 1 producer.  I send 1 message, and the first worker grabs it, and waits the 20 seconds, but what I'm expecting is after 10seconds the message is given to the 2nd worker as the first worker didn't call the channel.BasicAck in that 10 seconds.

Hope that helps.  Thank you so much!

[Michal Kuratczyk]

In the future, please try to provide something we can just execute. We had at least a few issue reports a day and

putting together the reproduction steps is really time consuming. The more we do that, the less time we have

for RabbitMQ development.

This is a test case I put together:

# publish a single message
perf-test -ad false -f persistent -qa x-queue-version=2,x-consumer-timeout=300000 -u q5m -y 0 -C 1

# start a consumer with very high latency
date; perf-test -ad false -f persistent -qa x-queue-version=2,x-consumer-timeout=300000 -u q5m -x 0 -D 1 -L 1000000000;date

# start another consumer that should get the message after the high-latency consumers times out
date; perf-test -ad false -f persistent -qa x-queue-version=2,x-consumer-timeout=300000 -u q5m -x 0 -D 1; date

It works, but it seems to be taking 1 minute longer to time out than expected (6 instead of 5, 11 instead of 10, when I used 600000).

This one extra minute seems to be a bug that I don't fully understand. However, this feature was never meant to be used with such low values.

The default is 30 minutes and people keep asking how to extend it, which is why this per-queue/per-consumer option was added.

While the extra minute seems to be a bug, the timeout is also not meant to be precise. So we might fix it, but please don't expect

that whatever you set will be enforced down to the second. The consumer timeout is a mechanism to make sure we can make progress

even if a consumer stopped responding, not to guarantee delivery in a certain time.

Best,

To view this discussion on the web, visit https://groups.google.com/d/msgid/rabbitmq-users/dea5b45e-ac9a-4d4e-945d-ca9631ddcb35n%40googlegroups.com.

--

Michał

RabbitMQ team

[Josh Holdaway]

Hello and thank you for the response.

I forked the dotnet samples and made the changes here:

https://github.com/Vx2gas/rabbitmq-tutorials/tree/bug/consumer-issue/dotnet

(Timeout set to 5 minutes, with the worker set to sleep for 10 minutes)

1. Run the NewTask project once to add a message

2. Run 2 instances of the worker project.

See the screenshot below of the worker instances, you will see the 2nd worker doesn't get message after the 5 minute timeout.  

What am I doing wrong?  

Thanks!

Josh

[Michal Kuratczyk]

Seems to be working for me (with the 1 extra minute caveat I created an issue for: https://github.com/rabbitmq/rabbitmq-server/issues/8221).

The second consumer received the messages 6 minutes after the first one.

> dotnet run
[*] Waiting for messages.
Press [enter] to exit.
[x] Received Hello World! on 5/18/2023 10:12:18 AM                                                                                                                                                                        [x] Done on 5/18/2023 10:22:18 AM

> date; dotnet run
Thu May 18 10:12:25 CEST 2023
[*] Waiting for messages.
Press [enter] to exit.                                                                                                                                                                                                                          [x] Received Hello World! on 5/18/2023 10:18:18 AM
[x] Done on 5/18/2023 10:28:18 AM

To view this discussion on the web, visit https://groups.google.com/d/msgid/rabbitmq-users/fbe173b3-6e3d-43f3-ae5c-a10d8cdd1970n%40googlegroups.com.

--

Michał

RabbitMQ team

[Josh Holdaway]

That's good news its working for you... However, it still is not working for me.  :-(

I updated to 3.11.16 to make sure I'm on the latest.

Does this all look good? 

Is there anything else I can check ?

[Josh Holdaway]

Also as a FYI, If use this environment variable in my docker compose and remove the per queue timeout, it works:

- RABBITMQ_SERVER_ADDITIONAL_ERL_ARGS=-rabbit consumer_timeout  300000

However, I would like to use the per queue timeout.

[Michal Kuratczyk]

Looking at the code, I don't really see how that may just not work at all unless you have consumer_tick_interval set to some non-standard value.

The default is 60s, which is why there's this one extra minute - it's only evaluated once a minute.

To view this discussion on the web, visit https://groups.google.com/d/msgid/rabbitmq-users/0017acea-cb3d-4c97-bbfe-3a8f16f58526n%40googlegroups.com.

--

Michał

RabbitMQ team

RabbitMQ team

[Josh Holdaway]

Yeah its strange.  I haven't changed anything else :-(