[
https://issues.apache.org/jira/browse/AIRFLOW-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15457747#comment-15457747
]
Wu Xiang commented on AIRFLOW-78:
---------------------------------
hi [~sanand],
This PR will prevent Airflow to process task instances for running DagRuns
when max_active_dag_runs reached.
This should be a bug, when max_active_dag_runs are reached, several things
should still be processed,
1) _process_task_instances for running dag runs
2) manage_slas for running dag runs
3) prevent generating new dag runs
relative line of code:
https://github.com/apache/incubator-airflow/blob/master/airflow/jobs.py#L1076
> 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)
