You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2021/01/06 03:13:00 UTC
[GitHub] [airflow] gbonazzoli commented on issue #13434: Airflow 2.0.0 manual run causes scheduled run to skip
gbonazzoli commented on issue #13434:
URL: https://github.com/apache/airflow/issues/13434#issuecomment-755048513
I don't know if my problem is related to this issue, but I want to underline a change of behavior in airflow 2.0.0 in how the **`max_active_runs`** directive works.
I have the following DAG definition:
```
with DAG('VMWARE_BACKUP',
description = 'VMWARE_BACKUP',
tags=['vmware'],
schedule_interval = None,
start_date = datetime(2019, 5, 29, tzinfo=local_tz),
default_args = default_args,
max_active_runs = 1, # maximum number of active runs for this DAG
concurrency = 1, # Added with Airflow 2.0.0
catchup = False
) as dag:
```
Before Airflow 2.0.0 only one DAG was allowed to run.
With Airflow 2.0.0 (probably due to the scheduler's rewriting with the fantastic speed added in switching between tasks) at the end of one task in a DAGrun instance instead of scheduling the following one it is scheduled a task from another DAGrun Instance, as you can se from the attached screenshot.
I can mitigate the problem in Airflow 2.0.0 with the added **`concurrency = 1`** so that at list the only very long task that I want to be the only one running on the system it runs alone....
It works in my use case in other circumstances it could be impracticable.
Please tell me if it is better to open a new main issue.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org