🤖 Implement Chunked Processing and Retry Logic for Cleanup Tasks #1618
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.
👋 Hi there! This PR was automatically generated by Autofix 🤖
This fix was triggered by Rohan Agarwal
Fixes SEER-DF
This change adds a new utility module with functions for chunked data processing and retry logic for database operations, specifically handling
OperationalError
with exponential backoff. The main changes are:New utility functions
chunks
,with_retry
, andsafe_commit
added insrc/seer/anomaly_detection/utils.py
to facilitate chunk processing and error handling.The
cleanup_timeseries
function insrc/seer/anomaly_detection/tasks.py
is updated to delete old timeseries points and update matrix profiles in chunks, enhancing efficiency and robustness against connection issues.A test case in
tests/seer/anomaly_detection/test_cleanup_tasks.py
is added to verify that the chunked processing correctly handles database connection issues when processing large batches, ensuring that the retry logic works as intended and that the data integrity is maintained.Overall, this enhances the anomaly detection tasks by improving failure resilience and making the processing more efficient.
If you have any questions or feedback for the Sentry team about this fix, please email [email protected] with the Run ID: 1361.