hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3092) Create common ResourceUsage class to track labeled resource usages in Capacity Scheduler
Date Tue, 27 Jan 2015 15:05:39 GMT

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

Hudson commented on YARN-3092:
------------------------------

FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #87 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/87/])
YARN-3092. Created a common ResourceUsage class to track labeled resource usages in Capacity
Scheduler. Contributed by Wangda Tan (jianhe: rev 6f9fe76918bbc79109653edc6cde85df05148ba3)
* hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/TestResourceUsage.java
* hadoop-yarn-project/CHANGES.txt
* hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/ResourceUsage.java


> Create common ResourceUsage class to track labeled resource usages in Capacity Scheduler
> ----------------------------------------------------------------------------------------
>
>                 Key: YARN-3092
>                 URL: https://issues.apache.org/jira/browse/YARN-3092
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: api, client, resourcemanager
>            Reporter: Wangda Tan
>            Assignee: Wangda Tan
>             Fix For: 2.7.0
>
>         Attachments: YARN-3092.1.patch, YARN-3092.2.patch
>
>
> Since we have labels on nodes, so we need to track resource usage *by labels*, includes
> - AM resource (to enforce max-am-resource-by-label after YARN-2637)
> - Used resource (includes AM resource usage)
> - Reserved resource
> - Pending resource
> - Headroom
> Benefits to have such a common class are:
> - Reuse lots of code in different places (Queue/App/User), better maintainability and
readability.
> - Can make fine-grained locking (e.g. accessing used resource in a queue doesn't need
lock a queue)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message