-
Notifications
You must be signed in to change notification settings - Fork 174
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
Redis dlq support #1478
Redis dlq support #1478
Conversation
8adfc31
to
8ae8326
Compare
bc06ac8
to
d82b4c6
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I left a minor nit, but otherwise LGTM.
Will we have admin endpoints for viewing the DLQ too?
Yeah we probably need it. Elsewhere we monitor the queue depth, so at a minimum I should probably just add that for now. Otherwise it's completely opaque what's going on w/ the queue since we create/manage it internally. |
a2a0b68
to
be6e7c2
Compare
This matches downstream changes and should make the integration of DLQ support seamless.
Add support for moving failed messages to deadletter queue in Redis. The queue can be re-driven via an undocumented endpoint, `/api/v1/admin/redrive-dlq`.
be6e7c2
to
75f243a
Compare
Bring in downstream changes to prevent flakes here.
For now, I've added metrics to monitor the DLQ (and other queues) via metrics (#1479). We can consider adding additional admin endpoints later, but for now the metrics will prevent DLQ contents from being completely opaque to the user. |
Add support for moving failed messages to deadletter queue in
Redis. The queue can be re-driven via an undocumented endpoint,
/api/v1/admin/redrive-dlq
.