Set the message retention period for the events and events_index prod…#265
Open
wendelfabianchinsamy wants to merge 1 commit intomasterfrom
Open
Conversation
…uction sqs queues to 10 days
Contributor
|
be careful about merging this. It will likely destroy/clear the current queue. |
Contributor
Author
Thanks @jrhoads. It seems that this is an "in place change" and therefore will not be destructive. However I do not intend on merging this soon. Will discuss with the team to get everyone's thoughts on such a long retention period. |
richardhallett
approved these changes
Oct 16, 2025
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
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.
…uction sqs queues to 10 days
Purpose
Increase the number of days a message can live on the events and events_index production SQS to 10 days from the default 4 days.
closes: Add github issue that originated this PR
Approach
Open Questions and Pre-Merge TODOs
Learning
Types of changes
Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to change)
Reviewer, please remember our guidelines: