[
https://issues.apache.org/jira/browse/AIRFLOW-1349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16114968#comment-16114968
]
ASF subversion and git services commented on AIRFLOW-1349:
----------------------------------------------------------
Commit ddc50269431d8715e0eaeed7be5f522fed5521da in incubator-airflow's branch
refs/heads/master from [~erod]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-airflow.git;h=ddc5026 ]
[AIRFLOW-1349] Fix backfill to respect limits
Before, if a backfill job was triggered that would
include a dag run
already in a RUNNING state, the dag run within the
backfill would be
included in the count agains the max_active_runs
limit. Also, if a
backfill job generated multiple dag runs it could
potentially
violate max_active_runs limits by executing all
dag runs.
Now the limit is checked per dag run to be
created, and the backfill job
will only run the dag runs within the backfill job
that could be
included within the limits.
Also, if the max_active_runs limit has already
been reached, the
BackfillJob will wait and loop trying to create
the required dag runs as
soon as a dag run slot within the limit is
available until all dag runs
are completed.
These changes provide a more consistent behavior
according to the
max_active_runs limits definition and allows the
user to run backfill
jobs with existing RUNNING state when already
considered within the
limits.
Closes #2454 from edgarRd/erod-fix-backfill-max
> Max active dagrun check for backfills shouldn't include the backfilled dagrun
> -----------------------------------------------------------------------------
>
> Key: AIRFLOW-1349
> URL: https://issues.apache.org/jira/browse/AIRFLOW-1349
> Project: Apache Airflow
> Issue Type: Bug
> Components: backfill
> Reporter: Dan Davydov
> Assignee: Edgar Rodriguez
>
> When you backfill a dag with e.g. 1 max active dagrun, if that dagrun is
> already running then it shouldn't count against the max active dagruns of the
> backfill and make the backfill fail.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
