[
https://issues.apache.org/jira/browse/AIRFLOW-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17014654#comment-17014654
]
ASF subversion and git services commented on AIRFLOW-1467:
----------------------------------------------------------
Commit 6df30a3ee78605e00376b3d2a0a537e27a6f20a9 in airflow's branch
refs/heads/master from Jarek Potiuk
[ https://gitbox.apache.org/repos/asf?p=airflow.git;h=6df30a3 ]
Revert "[AIRFLOW-1467] Dynamic pooling via allowing tasks to use more than one
pool slot (depending upon the need) (#6975)"
This reverts commit 277d01d4c57fe2470a8518c58bf0df9bf21e8f5e.
> allow tasks to use more than one pool slot
> ------------------------------------------
>
> Key: AIRFLOW-1467
> URL: https://issues.apache.org/jira/browse/AIRFLOW-1467
> Project: Apache Airflow
> Issue Type: Improvement
> Components: scheduler
> Reporter: Adrian Bridgett
> Priority: Trivial
> Labels: pool
> Fix For: 1.10.8
>
>
> It would be useful to have tasks use more than a single pool slot.
> Our use case is actually to limit how many tasks run on a head node (due to
> memory constraints), currently we have to set a pool limit limiting how many
> tasks.
> Ideally we could set the pool size to e.g amount of memory and then set those
> tasks pool_usage (or whatever the option would be called) to the amount of
> memory we think they'll use. This way the pool would let lots of small tasks
> run or just a few large tasks.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
