[
https://issues.apache.org/jira/browse/AIRFLOW-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15409653#comment-15409653
]
Adrian Bridgett commented on AIRFLOW-78:
----------------------------------------
I think so yes - it's possible that it's the opposite (that it didn't run _at
all_ due to max_active_runs being set).
I've just tried it in fact - this is on 1.7.1.3 so a bit newer.
I have a simple DAG (task A -> task B).
After clearing the last two days it currently shows in the tree view:
2016-08-03 (A success) (B running) (DAG running)
2016-08-04 (A null) (B null) (DAG failed)
...time passes...
And now:
2016-08-03 (A success) (B succes) (DAG success)
2016-08-04 (A null) (B null) (DAG failed)
...
> 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)
