feat: Add configurable visibility timeout renewal#6173
Merged
phatboyg merged 2 commits intoMassTransit:developfrom Dec 15, 2025
Merged
feat: Add configurable visibility timeout renewal#6173phatboyg merged 2 commits intoMassTransit:developfrom
phatboyg merged 2 commits intoMassTransit:developfrom
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
phatboyg
reviewed
Dec 14, 2025
sukanta1991
changed the title
This file contains hidden or 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
2 participants
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.
Made the visibility timeout extension configurable for Amazon SQS instead of the default 60 seconds. As there are use cases where in case of background task the compute is known to take more than 2 hours. In such cases if we use the default 60 seconds of extension when the default timeout of a message is set to 1 hour, 133 extra SQS api calls to complete this message operation, this can cause a significant AWS cost for message operations.
Having the capability to configure this make is more flexible.
I have tested this in my usecase, where the default timeout of the message is set to 1 hour and the message in average was taking nearly 2 hours to complete. After using this property to extend the visibility timeout for the message, I can see a significant reduction of the AWS SQS cost( used day to day comparison)
Points considered: