[ 
https://issues.apache.org/jira/browse/YARN-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13705794#comment-13705794
 ] 

Hudson commented on YARN-736:
-----------------------------

Integrated in Hadoop-Hdfs-trunk #1457 (See 
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/1457/])
    updating CHANGES.txt after committing 
MAPREDUCE-5333,HADOOP-9661,HADOOP-9355,HADOOP-9673,HADOOP-9414,HADOOP-9416,HDFS-4797,YARN-866,YARN-736,YARN-883
 to 2.1-beta branch (Revision 1502075)

     Result = FAILURE
tucu : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1502075
Files : 
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt

                
> 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
>             Fix For: 2.1.0-beta
>
>         Attachments: YARN-736-1.patch, YARN-736-2.patch, YARN-736-3.patch, 
> YARN-736-4.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

Reply via email to