You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Victor Vianna (JIRA)" <ji...@apache.org> on 2018/08/22 10:21:00 UTC

[jira] [Updated] (AIRFLOW-2934) Pools not respected for internal subdag tasks

     [ https://issues.apache.org/jira/browse/AIRFLOW-2934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Victor Vianna updated AIRFLOW-2934:
-----------------------------------
    Description: I'm trying to have some subdags execute one task at a time. The way I found was to create a first pool for the SubdagOperators (pool1 in the attached code file) and a second one for the internal tasks (pool2). However, it appears that pools for subdag elements are not being respected. Running airflow 1.9.0 with LocalExecutor.  (was: I'm trying to have some subdags execute one task at a time. The way I found was to create a first pool for the SubdagOperators (pool1 in the attached code file) and a second one for the internal tasks (pool2). However, it appears that pools for subdag elements are not being respected. Running airflow 1.9.0.)

> Pools not respected for internal subdag tasks
> ---------------------------------------------
>
>                 Key: AIRFLOW-2934
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-2934
>             Project: Apache Airflow
>          Issue Type: Bug
>          Components: pools, subdag
>    Affects Versions: 1.9.0
>         Environment: Linux victorvianna 4.14.65-1-MANJARO #1 SMP PREEMPT Sat Aug 18 13:29:56 UTC 2018 x86_64 GNU/Linux
>            Reporter: Victor Vianna
>            Priority: Blocker
>         Attachments: dag_pool.py
>
>
> I'm trying to have some subdags execute one task at a time. The way I found was to create a first pool for the SubdagOperators (pool1 in the attached code file) and a second one for the internal tasks (pool2). However, it appears that pools for subdag elements are not being respected. Running airflow 1.9.0 with LocalExecutor.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)