AMQP: added custom delayed queue config #796
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary:
This pull request introduces a configurable option to specify a custom delayed queue in the AMQP configuration. The goal is to allow users to have greater flexibility in handling delayed tasks without the need to create multiple delayed queues in Machinery.
Changes:
Added a new configuration parameter DelayedQueue to the AMQP configuration.
The DelayedQueue parameter allows users to set a custom name for the delayed queue.
Motivation:
Currently, Machinery create multiple queue when we choose task with retry or delayed task. This limited the scaleability when we have millions of delayed task.
Usages:
This feature can be used if env variables AMQP_DELAYED_QUEUE is set else it will continued with current approach in both v1 and v2.