Hey people! When developing locally, I have configured my queue with following retry timeouts and c
Hey people!
When developing locally, I have configured my queue with following retry timeouts and counts:
I noticed that for some unknown reason, the retry logic only attempts up to 3 times. If I lower the retry_delay to 10 seconds, I can reach 6th attempt. If I finally lower the delay to 2 seconds, I can reach 10 retry attempts which is expected.
Any ideas, why the 30s delay is not working and 2 seconds is? 🤔
14 Replies
it's possible to list messages inside dead queue?
You can do it via the dashboard. If you want to use http then you could configure a pull consumer for the dlq
So I would need to implement my own api to retrieve the dlq messages?
Cloudflare Docs
Pull consumers | Cloudflare Queues
A pull-based consumer allows you to pull from a queue over HTTP from any environment and/or programming language outside of Cloudflare Workers. A pull-based consumer can be useful when your message consumption rate is limited by upstream infrastructure or long-running tasks.
Cloudflare API Documentation
Interact with Cloudflare's products and services via the Cloudflare API
Thanks
Dead letter queues behave just like normal queues. You could setup a consumer, just like you would with a normal queue. It doesn't necessarily need to be a pull consumer; you could use a worker too.
But I would need to store the messages somewhere
I don’t want to need to add an extra db only for this
Ideally queues could allows us to list pending messages
is there a way of getting the name of the queue, when you have the queue object?
Hi everyone! I am starting looking into using queues but have one question...can I configure a worker script as a queue consumer through terraform? I havent found the setup yet..still looking but if anyone here knows or can point me to the info...
it looks like I can configure the queue reference on a worker to send a message but I need to configure the consumer through terraform also.
or is it just a worker with the queue() function? hmm...Ill try it
hmmm...its not picking up my worker as a consumer... is there a way to configure a queue consumer through terraform?
never used terraform for it - sorry
Is there a way to force a queue to increase concurrency, or to set a minimum concurrency?
I'm seeing the following behaviour now:
I have a queue where only once every 1-5 minutes, a message is queued. A message takes about 30 seconds wall time to be processed. Maximum consumer concurrency is on default.
But, when a message comes in that all of a sudden takes 30 minutes to process, the whole queue will be stuck until that one message is processed (that's the behaviour I'm observing at least). This behaviour is in line with the docs, since Queues will only check after processing a batch of messages if the concurrent consumers should be adjusted.
Very annoying behaviour of course - because of a slow message, I suddenly have messages waiting for 30 minutes in the queue. Only after the message is processed, the concurrency will be updated and all waiting messages will be handled. Being able to set a minimum concurrency would be a big help here
anyone else see queue send failures across of dozens of colos at around 2024-08-26 06:21:46 UTC?
Error: Queue send failed: Internal Server Error
Haven't seen anything across so many colos at once like this before@Pranshu Maheshwari