[
https://issues.apache.org/jira/browse/AIRFLOW-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15408919#comment-15408919
]
Maxime Beauchemin commented on AIRFLOW-78:
------------------------------------------
The idea behind `clear` is more of a way to get task instances to re-run, by
clearing their `failed` state (problems has been fixed, we're ready to re-run)
or by clearing a `success` state ("hey, this was a false positive!", or "source
data was wrong, let's rerun this"). When it is the intent, we want the
scheduler to pick those tasks up and re-run them, this is why we re-activate
the DagRuns.
Maybe the docs need to be clarified. Maybe we need some sort of a
`--dont-reactivate-dagruns` flag as well.
> 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)
