-
Notifications
You must be signed in to change notification settings - Fork 5
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
Messages barrier max time #141
Conversation
@@ -30,6 +31,7 @@ import { AbstractSqsService } from './AbstractSqsService' | |||
const ABORT_EARLY_EITHER: Either<'abort', never> = { | |||
error: 'abort', | |||
} | |||
const DEFAULT_MAX_RETRY_DURATION = 4 * 24 * 60 * 60 // 4 days in seconds |
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 think 4 days is the default time a message can be in the queue waiting, will check to make sure
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.
Confirmed (doc) using the same value on AMQP to have similar behaviour in both, please let me know if you disagree
Co-authored-by: Igor Savin <[email protected]>
…ibertoad/message-queue-toolkit into feat/messages_barrier_max_time
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.
Excellent job as always, Carlos!
Co-authored-by: Daria Carlotta Maino <[email protected]>
Co-authored-by: Daria Carlotta Maino <[email protected]>
Description
If a message fails to be processed, and is there another message waiting for it on the barrier pattern, it will be there waiting forever.
Solution:
retryLater
feature