Reduce the chance of database locks interrupting soud syncing. #11886
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.
Summary
Wraps the SyncQueue save method in the
retry_on_db_lock
decorator to reduce the chances of interrupting the SOUD sync queue because of a database locked error.References
Based on database locked errors seen in #11816 (comment)
Addresses the general case seen in this error traceback from the above:
Reviewer guidance
Could this have any unexpected negative side effects? This feels like the right thing to do, as we already use exactly the same decoration mechanism to protect sync queue update or create from database locked errors in the sync hooks.
Testing checklist
PR process
Reviewer checklist
yarn
andpip
)