[
https://issues.apache.org/jira/browse/YARN-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13682740#comment-13682740
]
Hadoop QA commented on YARN-736:
--------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12587698/YARN-736-1.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 4 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}. The javadoc tool did not generate any
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 1.3.9) 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-server/hadoop-yarn-server-resourcemanager
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/1224//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/1224//console
This message is automatically generated.
> Add a multi-resource fair sharing metric
> ----------------------------------------
>
> Key: YARN-736
> URL: https://issues.apache.org/jira/browse/YARN-736
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: scheduler
> Affects Versions: 2.0.4-alpha
> Reporter: Sandy Ryza
> Assignee: Sandy Ryza
> Attachments: YARN-736-1.patch, YARN-736.patch
>
>
> Currently, at a regular interval, the fair scheduler computes a fair memory
> share for each queue and application inside it. This fair share is not used
> for scheduling decisions, but is displayed in the web UI, exposed as a
> metric, and used for preemption decisions.
> With DRF and multi-resource scheduling, assigning a memory share as the fair
> share metric to every queue no longer makes sense. It's not obvious what the
> replacement should be, but probably something like fractional fairness within
> a queue, or distance from an ideal cluster state.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
