Mailing-List: contact commits-help@airflow.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@airflow.incubator.apache.org
Date: Tue, 16 May 2017 05:14:04 +0000 (UTC)
From: "Christian Rodriguez (JIRA)" <jira@apache.org>
To: commits@airflow.incubator.apache.org
Message-ID: <JIRA.12971085.1463648643000.217735.1494911644708@Atlassian.JIRA>
In-Reply-To: <JIRA.12971085.1463648643000@Atlassian.JIRA>
References: <JIRA.12971085.1463648643000@Atlassian.JIRA> <JIRA.12971085.1463648643352@jira-lw-us.apache.org>
Subject: [jira] [Comment Edited] (AIRFLOW-137) Airflow does not respect
 'max_active_runs' when task from multiple dag runs cleared
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 16 May 2017 05:14:10 -0000


    [ https://issues.apache.org/jira/browse/AIRFLOW-137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16011750#comment-16011750 ] 

Christian Rodriguez edited comment on AIRFLOW-137 at 5/16/17 5:13 AM:
----------------------------------------------------------------------

This is still an issue for backfill in 1.8.1 regardless of whether max_active_runs is set in airflow.cfg or the DAG definition. As Tomasz said, limiting with concurrency works, but causes strange scheduling behavior including hangs.

I think this is more than just a minor issue tbh...


was (Author: mrchrisrodriguez):
This is still an issue for backfill regardless of whether max_active_runs is set in airflow.cfg or the DAG definition. As Tomasz said, limiting with concurrency works, but causes strange scheduling behavior including hangs.

I think this is more than just a minor issue tbh...

> Airflow does not respect 'max_active_runs' when task from multiple dag runs cleared
> -----------------------------------------------------------------------------------
>
>                 Key: AIRFLOW-137
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-137
>             Project: Apache Airflow
>          Issue Type: Bug
>            Reporter: Tomasz Bartczak
>            Priority: Minor
>
> Also requested at https://github.com/apache/incubator-airflow/issues/1442
> Dear Airflow Maintainers,
> Environment
> Before I tell you about my issue, let me describe my Airflow environment:
> Please fill out any appropriate fields:
>     Airflow version: 1.7.0
>     Airflow components: webserver, mysql, scheduler with celery executor
>     Python Version: 2.7.6
>     Operating System: Linux Ubuntu 3.19.0-26-generic Scheduler runs with --num-runs and get restarted around every minute or so
> Description of Issue
> Now that you know a little about me, let me tell you about the issue I am having:
>     What did you expect to happen?
>     After running 'airflow clear -t spark_final_observations2csv -s 2016-04-07T01:00:00 -e 2016-04-11T01:00:00 MODELLING_V6' I expected that this task gets executed in all dag-runs in specified by given time-range - respecting 'max_active_runs'
>     Dag configuration:
>     concurrency= 3,
>     max_active_runs = 2,
>     What happened instead?
>     Airflow at first started executing 3 of those tasks, which already violates 'max_active_runs', but it looks like 'concurrency' was the applied limit here.
>     3_running_2_pending
> After first task was done - airflow scheduled all other tasks, making it 5 running dags at the same time that violates all specified limit.
> In the GUI we saw red warning (5/2 Dags running ;-) )
> Reproducing the Issue
> max_active_runs is respected in a day-to-day basis - when of the tasks was stuck - airflow didn't start more than 2 dags concurrently.
> [screenshots in the original issue: https://github.com/apache/incubator-airflow/issues/1442]


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)