ChristianYeah opened a new issue #9131:
URL: https://github.com/apache/airflow/issues/9131
**Apache Airflow version**: 1.10.10
**Environment**:
- **Cloud provider or hardware configuration**:
- **OS** (e.g. from /etc/os-release): centos 7.5
- **Kernel** (e.g. `uname -a`):Linux prod-auto-ops001
3.10.0-1062.4.1.el7.x86_64 #1 SMP Fri Oct 18 17:15:30 UTC 2019 x86_64 x86_64
x86_64 GNU/Linux
- **Install tools**: pip
- **Others**:
**What happened**:
I have two environments, one is development, another is production. They
uses CeleryExecutor and redis for broker, mysql for result backend and the
airflow db. The only difference is production env got two worker.
I passed the params, max_active_runs in my dag defination , eg:
```
dag = DAG(
dag_id='test_max_active_runs',
default_args=default_args,
schedule_interval=None,
start_date=airflow.utils.dates.days_ago(1),
max_active_runs=1
)
```
In the dev env, when the task is scheduled, the dashboard will show 1/1
active dag runs in red color, while nothing happens in the production env.
May I suppose that the setting max_active_runs is not working in my
production env?
**What you expected to happen**:
It should be exactly the same in the production env comparison to the dev
env.
**How to reproduce it**:
Let me know if you need further information
----------------------------------------------------------------
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:
[email protected]
