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

Sunil G commented on YARN-4161:
-------------------------------

I got your point. I was trying to point out to an existing configuration in CS 
named 
*yarn.scheduler.capacity.per-node-heartbeat.maximum-offswitch-assignments*. I 
thought of keep this syntax and it seems more of similar nature to me.

bq.We still need assignMultiple one, as maxAssign=-1 mostly means 
(assignMultiple is enabled, and the max allowed allocation is unlimited).
Thanks for clarifying. I understood the reason behind that. On an another note, 
maxAssign=0 is meaning less. Correct? So value less than 0 could be considered 
for infinite. And a boolean variable to switch-on / off the feature.

Few more doubts.
# I think assignMultiple should not impact existing 
"maximum-offswitch-assignments" feature. I can see that current patch will skip 
when assignMultiple is configured as false.
# Could we rename assignMultiple to something like 
assign-multiple-containers-per-heartbeat
# Are you planning to consider this per queue as well ? Or only at CS level 
from top for now.


> Capacity Scheduler : Assign single or multiple containers per heart beat 
> driven by configuration
> ------------------------------------------------------------------------------------------------
>
>                 Key: YARN-4161
>                 URL: https://issues.apache.org/jira/browse/YARN-4161
>             Project: Hadoop YARN
>          Issue Type: New Feature
>          Components: capacity scheduler
>            Reporter: Mayank Bansal
>            Assignee: Mayank Bansal
>              Labels: oct16-medium
>         Attachments: YARN-4161.patch, YARN-4161.patch.1
>
>
> Capacity Scheduler right now schedules multiple containers per heart beat if 
> there are more resources available in the node.
> This approach works fine however in some cases its not distribute the load 
> across the cluster hence throughput of the cluster suffers. I am adding 
> feature to drive that using configuration by that we can control the number 
> of containers assigned per heart beat.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to