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 subversion and git services (JIRA)" <ji...@apache.org> on 2019/07/01 15:39:00 UTC

[jira] [Commented] (AIRFLOW-4591) Tag tasks with default pool

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

ASF subversion and git services commented on AIRFLOW-4591:
----------------------------------------------------------

Commit 6c5c01849a109c278a1260a1bdaa9fe215e10f2b in airflow's branch refs/heads/v1-10-stable from Ash Berlin-Taylor
[ https://gitbox.apache.org/repos/asf?p=airflow.git;h=6c5c018 ]

[AIRFLOW-4591] Fixup delete pool in classic UI

In backporting the "Make default_pool a real pool" feature in to
a7ab1702a I left in a ipdb.set_trace()


> Tag tasks with default pool
> ---------------------------
>
>                 Key: AIRFLOW-4591
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-4591
>             Project: Apache Airflow
>          Issue Type: New Feature
>          Components: core
>    Affects Versions: 2.0.0
>            Reporter: Chao-Han Tsai
>            Assignee: Chao-Han Tsai
>            Priority: Major
>             Fix For: 1.10.4
>
>
> Currently the number of running tasks without a pool specified will be limited by `non_pooled_task_slot_count`. It limits the number of tasks launched per scheduler loop but does not limit the number of tasks running in parallel.
> This ticket proposes that we assign tasks without a pool specified to default pool which limits the number of running tasks in parallel.



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