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

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

Commit 277d01d4c57fe2470a8518c58bf0df9bf21e8f5e in airflow's branch 
refs/heads/master from Lokesh Lal
[ https://gitbox.apache.org/repos/asf?p=airflow.git;h=277d01d ]

[AIRFLOW-1467] Dynamic pooling via allowing tasks to use more than one pool 
slot (depending upon the need) (#6975)

* adding pool capacity required for each task for dynamic pooling

* Added pool_capacity column migration script

* removed test checkedin file

* removed extra space

* correct test_database_schema_and_sqlalchemy_model_are_in_sync test case

* Added description for pool_capacity property for task instance

* Modified test cases to include pool_capacity along with pool in task instances

* Modified test cases to include pool_capacity along with pool in task instances

* Removed Column.name property, since property value is same as actual variable

* check for pool_capacity property to be always >= 1

* removed unused variable ti

* modified test cases for pool_capacity

* modified test cases for pool_capacity


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

Reply via email to