Change Delay Queue's TTL
See original GitHub issueIn my setup I have multiple queues with various delays and these delays are configurable, so as I made some search if I want to change any config of a queue I need to create a new queue then migrate messages in the old queue to the new one and then delete the old one. I tried to find something to help me achieve this with rascal
but couldn’t find anything to help me delete a queue/exchange/binding from the exposed API.
I really liked this tool and I’m thinking of using it in my app instead of the amqplib
because of the reasons mentioned here.
So do you have any suggestion on how I might do this?
Issue Analytics
- State:
- Created 4 years ago
- Comments:16 (9 by maintainers)
Top Results From Across the Web
RabbitMQ Delayed Messages 101: How to Delay & Schedule ...
1) Using TTL and DLX to Delay Message Delivery · Declare the pending queue · Set the x-dead-letter-exchange argument property to the default...
Read more >Time-To-Live and Expiration - RabbitMQ
RabbitMQ allows you to set TTL (time to live) for both messages and queues. Expired messages and queues will be deleted: the specifics...
Read more >Amazon SQS delay queues - Amazon Simple Queue Service
Delay queues let you postpone the delivery of new messages to consumers for a number of seconds, for example, when your consumer application...
Read more >Delayed processing in RabbitMQ with Dead Letter Exchanges
The delay queue has a message TTL configured on it, ... A queue in RabbitMQ must be deleted to change settings and reuse...
Read more >RabbitMQ Delayed Delivery - Particular Software
The queue for the delay level is declared with an x-message-ttl value corresponding to 2^level seconds. The queue is also declared with an...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It wasn’t related to this issue. The reason is so users can independently update amqplib to a later compatible release without waiting for me to release a new version of rascal.
broker.connect
added in rascal@3.4.0 FYI I also moved amqplib to a peer dependency.