[
https://issues.apache.org/jira/browse/YARN-2531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14129974#comment-14129974
]
Hadoop QA commented on YARN-2531:
---------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12668046/apache-yarn-2531.0.patch
against trunk revision 4be9517.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/4890//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/4890//console
This message is automatically generated.
> CGroups - Admins should be allowed to enforce strict cpu limits
> ---------------------------------------------------------------
>
> Key: YARN-2531
> URL: https://issues.apache.org/jira/browse/YARN-2531
> Project: Hadoop YARN
> Issue Type: Improvement
> Reporter: Varun Vasudev
> Assignee: Varun Vasudev
> Attachments: apache-yarn-2531.0.patch
>
>
> From YARN-2440 -
> {quote}
> The other dimension to this is determinism w.r.t performance. Limiting to
> allocated cores overall (as well as per container later) helps orgs run
> workloads and reason about them deterministically. One of the examples is
> benchmarking apps, but deterministic execution is a desired option beyond
> benchmarks too.
> {quote}
> It would be nice to have an option to let admins to enforce strict cpu limits
> for apps for things like benchmarking, etc. By default this flag should be
> off so that containers can use available cpu but admin can turn the flag on
> to determine worst case performance, etc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
