Uh oh!
There was an error while loading. Please reload this page.
[v3-2-test] Prevent AlreadyRunningBackfill error caused by invalid date range request (#66874) - #67250
Merged
Merged
Conversation
choo121600
requested review from
XD-DENG, ashb, bugraoz93, ephraimbuddy, jason810496, pierrejeambrun, rawwar and shubhamraj-git
as code ownersMay 20, 2026 16:01
vatsrahul1001
requested review from
Fokko, RNHTTR, amoghrajesh, bbovenzi, bolkedebruin, dheerajturaga, gopidesupavan, guan404ming, hussein-awala, jedcunningham, josh-fell, jscheffl, kaxil, o-nikolas, potiuk, ryanahamilton, shahar1, vatsrahul1001 and vincbeck
as code ownersMay 21, 2026 03:11
apache#66865) * Fix OTel timer metrics using Gauge instead of Histogram * Use ExponentialBucketHistogramAggregation for timing metrics * Use public API import path for ExponentialBucketHistogramAggregation and fix histogram map isolation (cherry picked from commit b2dadd2) Co-authored-by: namratachaudhary <namratachaudhary@users.noreply.github.com>
…te range request (apache#66874) When a backfill is requested with from_date after to_date, the Backfill record was committed before _get_info_list() returned an empty list, leaving an orphaned record that blocked subsequent backfills with AlreadyRunningBackfill until the scheduler's 2-minute cleanup ran. Add an InvalidBackfillDateRange exception and validate from_date <= to_date at the top of _validate_backfill_params(), before any DB operations. (cherry picked from commit 1536238)
vatsrahul1001force-pushed
the
backport-66874-v3-2-test
branch
from
May 21, 2026 03:49
9712ec4 to
55fb2a0Comparebbovenzi
approved these changes
May 21, 2026
Uh oh!
There was an error while loading. Please reload this page.
vatsrahul1001 added a commit
that referenced
this pull request
May 25, 2026
…te range request (#66874) (#67250) * Fix OTel timer metrics using Gauge instead of Histogram (#64207) (#66865) * Fix OTel timer metrics using Gauge instead of Histogram * Use ExponentialBucketHistogramAggregation for timing metrics * Use public API import path for ExponentialBucketHistogramAggregation and fix histogram map isolation (cherry picked from commit b2dadd2) Co-authored-by: namratachaudhary <namratachaudhary@users.noreply.github.com> * [v3-2-test] Prevent AlreadyRunningBackfill error caused by invalid date range request (#66874) When a backfill is requested with from_date after to_date, the Backfill record was committed before _get_info_list() returned an empty list, leaving an orphaned record that blocked subsequent backfills with AlreadyRunningBackfill until the scheduler's 2-minute cleanup ran. Add an InvalidBackfillDateRange exception and validate from_date <= to_date at the top of _validate_backfill_params(), before any DB operations. (cherry picked from commit 1536238) --------- Co-authored-by: Rahul Vats <43964496+vatsrahul1001@users.noreply.github.com> Co-authored-by: namratachaudhary <namratachaudhary@users.noreply.github.com> Co-authored-by: Park Jiwon <57484954+david-parkk@users.noreply.github.com>
vatsrahul1001 added a commit
that referenced
this pull request
May 25, 2026
…te range request (#66874) (#67250) * Fix OTel timer metrics using Gauge instead of Histogram (#64207) (#66865) * Fix OTel timer metrics using Gauge instead of Histogram * Use ExponentialBucketHistogramAggregation for timing metrics * Use public API import path for ExponentialBucketHistogramAggregation and fix histogram map isolation (cherry picked from commit b2dadd2) Co-authored-by: namratachaudhary <namratachaudhary@users.noreply.github.com> * [v3-2-test] Prevent AlreadyRunningBackfill error caused by invalid date range request (#66874) When a backfill is requested with from_date after to_date, the Backfill record was committed before _get_info_list() returned an empty list, leaving an orphaned record that blocked subsequent backfills with AlreadyRunningBackfill until the scheduler's 2-minute cleanup ran. Add an InvalidBackfillDateRange exception and validate from_date <= to_date at the top of _validate_backfill_params(), before any DB operations. (cherry picked from commit 1536238) --------- Co-authored-by: Rahul Vats <43964496+vatsrahul1001@users.noreply.github.com> Co-authored-by: namratachaudhary <namratachaudhary@users.noreply.github.com> Co-authored-by: Park Jiwon <57484954+david-parkk@users.noreply.github.com>
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
When a backfill is requested with from_date after to_date, the Backfill record was committed before _get_info_list() returned an empty list, leaving an orphaned record that blocked subsequent backfills with AlreadyRunningBackfill until the scheduler's 2-minute cleanup ran.
Add an InvalidBackfillDateRange exception and validate from_date <= to_date at the top of _validate_backfill_params(), before any DB operations.
(cherry picked from commit 1536238)
#66874
Was generative AI tooling used to co-author this PR?
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.