Make locking behaviour more robust #205
Merged
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
Collaborator
ThrawnCA
commented
Jan 29, 2024
ThrawnCA
commented
- Use TRUNCATE with a short locking timeout, instead of dropping and recreating a table, when data structure has not changed
- Retry jobs that fail due to locking problems
- Acquire write locks up front when updating resource metadata so race conditions don't cause deadlock
- Shorten the locking timeout when refreshing a resource without changing its structure - Retry jobs that fail due to locking issues
- Request a write-lock when preparing to update resource metadata, not just a read lock, so that we don't risk deadlocking with another process.
duttonw
approved these changes
Jan 29, 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.