[
https://issues.apache.org/jira/browse/AIRFLOW-6251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
t oo updated AIRFLOW-6251:
--------------------------
Description:
airflow is often shared between users of varying experience levels. to prevent
a novice user causing a accidental denial of service to the scheduler (by
uploading huge dag which hogs all scheduler resources) i propose 2 new server
side configs:
# max num of tasks in a single dag: default say 250
# max num of dags: default say 500
To add to this airflow can't handle 18k tasks in single dag
(dag_processor_manager times out after 300 seconds) , but if i split up into 6
dags of 3k tasks each then it works.
was:
airflow is often shared between users of varying experience levels. to prevent
a novice user causing a accidental denial of service to the scheduler (by
uploading huge dag which hogs all scheluers resources) i propose 2 new server
side configs:
# max num of tasks in a single dag: default say 250
# max num of dags: default say 500
> add config for max tasks per dag and max num dags to prevent scheduler denial
> of service
> ----------------------------------------------------------------------------------------
>
> Key: AIRFLOW-6251
> URL: https://issues.apache.org/jira/browse/AIRFLOW-6251
> Project: Apache Airflow
> Issue Type: New Feature
> Components: scheduler
> Affects Versions: 1.10.6
> Reporter: t oo
> Priority: Major
>
> airflow is often shared between users of varying experience levels. to
> prevent a novice user causing a accidental denial of service to the scheduler
> (by uploading huge dag which hogs all scheduler resources) i propose 2 new
> server side configs:
>
> # max num of tasks in a single dag: default say 250
> # max num of dags: default say 500
>
> To add to this airflow can't handle 18k tasks in single dag
> (dag_processor_manager times out after 300 seconds) , but if i split up into
> 6 dags of 3k tasks each then it works.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
