You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Daniel Huang (JIRA)" <ji...@apache.org> on 2017/09/20 21:06:00 UTC
[jira] [Work started] (AIRFLOW-1627) SubDagOperator initialization
should only query pools when necessary
[ https://issues.apache.org/jira/browse/AIRFLOW-1627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on AIRFLOW-1627 started by Daniel Huang.
---------------------------------------------
> SubDagOperator initialization should only query pools when necessary
> --------------------------------------------------------------------
>
> Key: AIRFLOW-1627
> URL: https://issues.apache.org/jira/browse/AIRFLOW-1627
> Project: Apache Airflow
> Issue Type: Improvement
> Components: operators, subdag
> Reporter: Daniel Huang
> Assignee: Daniel Huang
> Priority: Minor
>
> If a SubDagOperator is assigned to a pool, it queries db for pool info to ensure there is no pool conflict with one of its tasks when only 1 slot remains. However, we should check that there's a possible conflict (a task in the subdag is in the same pool as the subdag) before actually querying for pools.
> I have a DAG with hundreds of subdags and I found that the pool conflict check was taking up a fair chunk of time when processing the DAG file.
> Relevant code: https://github.com/apache/incubator-airflow/blob/a81c153cc48e4c99a9e0a5047990b84c5d07e3cb/airflow/operators/subdag_operator.py#L60-L81
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)