-
Notifications
You must be signed in to change notification settings - Fork 22
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
[S3 realibility] Redeliver event dead letters to the queue #1253
Comments
hungphan227
changed the title
[S3 realibility] Rederliver event dead letters to the queue
[S3 realibility] Redeliver event dead letters to the queue
Oct 18, 2024
welcome any thoughts on this |
@chibenwa if you have other thoughts please comment |
Sounds ok to me |
Maybe make this a James ticket as it would benefit |
I think this would be the simplest indeed:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Why
When one of S3 is down for a long time, blob events would be stored in event dead letters table. James already has a task to redeliver dead letters back to the queue.
Unfortunately, EventDeadLettersRedeliverService (single instance) only has one EventDeadLetters instance -> only one EventSerializer instance (currently it is MailboxEventSerializer). Therefore, it does not work with blob event dead letters.
Refactoring code is needed to apply EventDeadLettersRedeliverService for blob event dead letters
How
DoD
Integration tests
The text was updated successfully, but these errors were encountered: