[
https://issues.apache.org/jira/browse/YARN-4161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16113123#comment-16113123
]
Wei Yan commented on YARN-4161:
-------------------------------
Yes, here we introduce one more condition check. But by default, the new
condition check is always positive. So when upgrading to new YARN but with old
config files, the behavior is still the same. The new condition comes to play
only after users make some changes there, in that case, users should be aware
of this new things.
> 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: [email protected]
For additional commands, e-mail: [email protected]
