Add integration-specific job semaphores#962
Merged
rgalanakis merged 1 commit intomainfrom Jun 3, 2025
Merged
Conversation
We need to migrate from a non-partitioned to a partitioned google calendar events table, which is billions of rows (or very large, in any case). If we just allow this to start backfilling, it will saturate all the workers for the org, and also consume a ton of DB CPU (though everything works). To prevent this from happening, we can semaphore the integration in particular.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #962 +/- ##
==========================================
- Coverage 96.97% 96.96% -0.01%
==========================================
Files 483 483
Lines 30729 30740 +11
==========================================
+ Hits 29798 29808 +10
- Misses 931 932 +1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
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
1 participant
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.
We need to migrate from a non-partitioned to a partitioned google calendar events table, which is billions of rows (or very large, in any case).
If we just allow this to start backfilling, it will saturate all the workers for the org, and also consume a ton of DB CPU (though everything works). To prevent this from happening, we can semaphore the integration in particular.