feat: Add option for valid time range to delete expired messages #1614
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
• Introduced a new configuration option to specify a valid time range for deleting expired messages. • Updated the deletion logic to respect the configured time range, allowing deletions to occur only during specified hours (e.g., 1 AM to 6 AM). • This change helps to avoid database locks during high load periods.
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.
• Introduced a new configuration option to specify a valid time range for deleting expired messages.
• Updated the deletion logic to respect the configured time range, allowing deletions to occur only during specified hours (e.g., 1 AM to 6 AM).
• This change helps to avoid database locks during high load periods.
Description:
This PR introduces a new configuration option to specify a valid time range for deleting expired messages. The deletion logic has been updated to respect the configured time range, allowing deletions to occur only during specified hours (e.g., 1 AM to 6 AM). This change helps to avoid database locks during high load periods.
Issue(s) addressed:
Affected components:
How to test:
Checklist: