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-3489) RMServerUtils.validateResourceRequests should only obtain queue info once
Date Tue, 12 May 2015 12:04:11 GMT

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

Hudson commented on YARN-3489:
------------------------------

SUCCESS: Integrated in Hadoop-Yarn-trunk #925 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk/925/])
YARN-3489. RMServerUtils.validateResourceRequests should only obtain queue info once. (Varun
Saxena via wangda) (wangda: rev d6f6741296639a73f5306e3ebefec84a40ca03e5)
* hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/RMServerUtils.java
* hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/SchedulerUtils.java
* hadoop-yarn-project/CHANGES.txt


> RMServerUtils.validateResourceRequests should only obtain queue info once
> -------------------------------------------------------------------------
>
>                 Key: YARN-3489
>                 URL: https://issues.apache.org/jira/browse/YARN-3489
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: resourcemanager
>    Affects Versions: 2.6.0
>            Reporter: Jason Lowe
>            Assignee: Varun Saxena
>              Labels: BB2015-05-RFC
>         Attachments: YARN-3489-branch-2.7.patch, YARN-3489.01.patch, YARN-3489.02.patch,
YARN-3489.03.patch
>
>
> Since the label support was added we now get the queue info for each request being validated
in SchedulerUtils.validateResourceRequest.  If validateResourceRequests needs to validate
a lot of requests at a time (e.g.: large cluster with lots of varied locality in the requests)
then it will get the queue info for each request.  Since we build the queue info this generates
a lot of unnecessary garbage, as the queue isn't changing between requests.  We should grab
the queue info once and pass it down rather than building it again for each request.



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

Mime
View raw message