IPS-596: Update TxMA Retention period and visibility timeout #355
Conversation
This file contains 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
|
vam-gds
approved these changes
Feb 16, 2024
|
👍 |
ViveakV
approved these changes
Feb 19, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
TxMa did a recent load test where they encountered some issues. To fix the issues they have mentioned that all teams using their service and producing events to update their SQS Queues.
Proposed changes
What changed
Message Retention Period - 7 days to 14 days
Message Visibility Timeout - 60 Seconds to 70 Seconds
Why did it change
Found issues with TxMA Load tests
Issue tracking
Checklists
PII logging
Environment variables or secrets
Other considerations