[ https://issues.apache.org/jira/browse/YARN-4161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16112855#comment-16112855 ]
Sunil G commented on YARN-4161: ------------------------------- Extremely sorry for sharing a quick doubt last moment here. bq.yarn.scheduler.capacity.per-node-heartbeat.maximum-offswitch-assignments After this patch, above config can work only if below conditions are met: # *yarn.scheduler.capacity.per-node-heartbeat.multiple-assignments-enabled* should be enabled. # {{(maxAssignPerHeartbeat == -1 || assignedContainers < maxAssignPerHeartbeat)}} should be +ve. This means that, existing behavior related to maximum-offswitch-assignments wont work provided above 2 cases are true. I think this is a regression. So i would like to point this to [~leftnoteasy] as well. Thoughts? > 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: Wei Yan > Labels: oct16-medium > Attachments: YARN-4161.002.patch, YARN-4161.003.patch, > YARN-4161.004.patch, YARN-4161.005.patch, YARN-4161.006.patch, > 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: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org