[
https://issues.apache.org/jira/browse/YARN-721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665039#comment-13665039
]
Hadoop QA commented on YARN-721:
--------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12584464/YARN-721.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{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.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/991//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/991//console
This message is automatically generated.
> ContainerManagerImpl failed to authorizeRequest
> -----------------------------------------------
>
> Key: YARN-721
> URL: https://issues.apache.org/jira/browse/YARN-721
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 2.0.3-alpha
> Reporter: PengZhang
> Attachments: YARN-721.patch
>
>
> When security is enabled, resource check will be failed. AM master cannot be
> launched.
> It reports like "Expected resource <memory:1800, vCores:1> but found
> <memory:1536, vCores:1>"
> I tracked this problem, and found it's imported in YARN-2. In
> RMAppAttemptImpl.ScheduleTransition, after allocate(), scheduler normalized
> Resource and created a new Resource object. Resource objects in scheduler and
> RMAppAttemptImp are used for schedule and launch separately. The difference
> value met in ContainerManagerImpl, and caused this problem.
--
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
