[
https://issues.apache.org/jira/browse/AIRFLOW-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15476471#comment-15476471
]
ASF subversion and git services commented on AIRFLOW-78:
--------------------------------------------------------
Commit 3a1be4aacf31ee33d6128e5d5fa563a7625c7c62 in incubator-airflow's branch
refs/heads/master from [~bolke]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-airflow.git;h=3a1be4a ]
Revert "[AIRFLOW-78] airflow clear leaves dag_runs"
This reverts commit 197c9050ef3a142c18aa97819da48ee8cadbf8d8.
Regressions were observed and tasks were not scheduled in case of
max_dag_runs reached.
> 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)
