hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zhijie Shen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-721) ContainerManagerImpl failed to authorizeRequest
Date Thu, 06 Jun 2013 21:48:20 GMT

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

Zhijie Shen commented on YARN-721:

The problem has already been fixed in YARN-370, and YARN-382. I think the problem should no
longer exist >= 2.0.3.
> 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,
> 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

View raw message