[
https://issues.apache.org/jira/browse/YARN-4963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15243219#comment-15243219
]
Wangda Tan commented on YARN-4963:
----------------------------------
[~nroberts], +1 to this feature, this gonna be very useful.
Instead of only limit #off-switch containers allocate per heartbeat, can we
limit #containers allocation regardless of locality? I can see some values to
limit #containers for rack/node locality as well. For example, if user wants
their containers allocated spread across all the cluster.
> capacity scheduler: Make number of OFF_SWITCH assignments per heartbeat
> configurable
> ------------------------------------------------------------------------------------
>
> Key: YARN-4963
> URL: https://issues.apache.org/jira/browse/YARN-4963
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: capacityscheduler
> Affects Versions: 3.0.0, 2.7.2
> Reporter: Nathan Roberts
> Assignee: Nathan Roberts
> Attachments: YARN-4963.001.patch
>
>
> Currently the capacity scheduler will allow exactly 1 OFF_SWITCH assignment
> per heartbeat. With more and more non MapReduce workloads coming along, the
> degree of locality is declining, causing scheduling to be significantly
> slower. It's still important to limit the number of OFF_SWITCH assignments to
> avoid densely packing OFF_SWITCH containers onto nodes.
> Proposal is to add a simple config that makes the number of OFF_SWITCH
> assignments configurable.
> Will upload candidate patch shortly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
