[v3-3-test] API: Return 503 when SQLite locks during backfill creation (#67900)#69659
Draft
github-actions[bot] wants to merge 1 commit into
Draft
[v3-3-test] API: Return 503 when SQLite locks during backfill creation (#67900)#69659github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
#67900) SQLite backfill creation via the REST API could return HTTP 500 and leave an orphan Backfill row when the scheduler and API server contend for the database, blocking retries with 409. Map lock errors to HTTP 503 with a clear message and clean up partial DagRuns and TaskInstances so users can retry against a clean slate. (cherry picked from commit 2fb2321) Co-authored-by: Lohit Kolluri <lohitkolluri@gmail.com> Signed-off-by: Lohit Kolluri <lohitkolluri@gmail.com>
boring-cyborg
Bot
added
area:API
1 task
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.
SQLite backfill creation via the REST API could return HTTP 500 and
leave an orphan Backfill row when the scheduler and API server contend
for the database, blocking retries with 409. Map lock errors to HTTP 503
with a clear message and clean up partial DagRuns and TaskInstances so
users can retry against a clean slate.
(cherry picked from commit 2fb2321)
Co-authored-by: Lohit Kolluri lohitkolluri@gmail.com
Signed-off-by: Lohit Kolluri lohitkolluri@gmail.com