[
https://issues.apache.org/jira/browse/YARN-3489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14548460#comment-14548460
]
Wangda Tan commented on YARN-3489:
----------------------------------
[~varun_saxena],
Tx for updating, I tried to run RM tests locally after applied the patch, a
couple of test failures:
Results :
Failed tests:
TestRMApplicationHistoryWriter.testRMWritingMassiveHistoryForCapacitySche:383->testRMWritingMassiveHistory:441
null
Tests in error:
TestAppManager.testRMAppSubmitDuplicateApplicationId:531 » NullPointer
TestAppManager.testRMAppSubmitMaxAppAttempts:506 » NullPointer
TestAppManager.testRMAppSubmit:463 » NullPointer
TestClientRMService.testAppSubmit:859 » NullPointer
TestClientRMService.testGetApplications:959 » NullPointer
TestClientRMService.testConcurrentAppSubmit:1115 » test timed out after 4000
...
Could you look at them?
> 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.02.patch,
> YARN-3489-branch-2.7.03.patch, 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)
