[ https://issues.apache.org/jira/browse/AIRFLOW-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15409046#comment-15409046 ]
Adrian Bridgett commented on AIRFLOW-78: ---------------------------------------- To confirm - I'm certainly happy that the tasks are rerun (we use this for the use cases that you listed), however I think what I saw here was that the tasks were immediately run - i.e. the max_active_runs constraint wasn't respected. (Hmm - rereading my earlier comments seems to suggest the opposite "it must have stopped any task from running at all"). Sorry to be so confused! > 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)