Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] Some transports block on a delayed requeue where not natively supported #3309

Open
iancooper opened this issue Sep 19, 2024 · 0 comments
Assignees
Labels
0 - Backlog Bug v10 Allocal to a v10 release

Comments

@iancooper
Copy link
Member

Describe the bug

Our API offers a delayed requeue where it is possible that the error is transient and could be fixed by simply returning to the queue with a delay. There are three responses we have:

  1. Native support for requeue with delay; we used this
  2. No native support for requeue and we requeue via a timer event that posts after the elapsed time window
  3. We block for the delay period then requeue

We know that 3 is never the right solution as this will block the whole pump, and pause message processing, not requeue with a delay. We should fix those transports that have the incorrect behavior.

Further technical details

  • The internal message consumer is a good example of how to get this right with a internal Requeue method that is called via a timer if delay is requested, and just passed through if not.
@iancooper iancooper added 0 - Backlog Bug v10 Allocal to a v10 release labels Sep 19, 2024
@iancooper iancooper self-assigned this Sep 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0 - Backlog Bug v10 Allocal to a v10 release
Projects
None yet
Development

No branches or pull requests

1 participant