You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/06/17 18:49:00 UTC

[jira] [Commented] (AIRFLOW-6251) add config for max tasks per dag to prevent scheduler denial of service

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

ASF GitHub Bot commented on AIRFLOW-6251:
-----------------------------------------

stale[bot] commented on pull request #7157:
URL: https://github.com/apache/airflow/pull/7157#issuecomment-645555462


   This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
   


----------------------------------------------------------------
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


> add config for max tasks per dag 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
>            Assignee: 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 new server side config: 
>  # max num of tasks in a single dag: if 0 then no limit
> 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)