[
https://issues.apache.org/jira/browse/AIRFLOW-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15414608#comment-15414608
]
ASF subversion and git services commented on AIRFLOW-78:
--------------------------------------------------------
Commit 197c9050ef3a142c18aa97819da48ee8cadbf8d8 in incubator-airflow's branch
refs/heads/master from [~normster]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-airflow.git;h=197c905 ]
[AIRFLOW-78] airflow clear leaves dag_runs
Fix a bug in the scheduler where dag runs cleared via CLI would be picked up
without checking max_active_dag_runs first, resulting in too many simultaneous
dag runs.
Dear Airflow Maintainers,
Please accept this PR that addresses the following issues:
- https://issues.apache.org/jira/browse/AIRFLOW-78
Testing Done:
- Expanded the jobs.test_scheduler_verify_max_active_runs test to test if
scheduler respects max_active_dag_runs
Fix a bug in the scheduler where dag runs cleared via CLI would be picked up
without checking max_active_dag_runs first, resulting in too many simultaneous
dag runs.
Closes #1716 from normster/clear_dagrun
> airflow clear leaves dag_runs
> -----------------------------
>
> Key: AIRFLOW-78
> URL: https://issues.apache.org/jira/browse/AIRFLOW-78
> Project: Apache Airflow
> Issue Type: Wish
> Components: cli
> Affects Versions: Airflow 1.6.2
> Reporter: Adrian Bridgett
> Assignee: Norman Mu
> Priority: Minor
>
> (moved from https://github.com/apache/incubator-airflow/issues/829)
> "airflow clear -c -d -s 2016-01-03 dagid" doesn't clear the dagrun, it sets
> it to running instead (apparently since this is often used to re-run jobs).
> However this then breaks max_active_runs=1 (I have to stop the scheduler,
> then airflow clear, psql to delete the dagrun, then start the scheduler).
> This problem was probably seen on an Airflow 1.6.x install.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
