You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "PengZhang (JIRA)" <ji...@apache.org> on 2013/05/23 11:25:21 UTC
[jira] [Updated] (YARN-721) ContainerManagerImpl failed to
authorizeRequest
[ https://issues.apache.org/jira/browse/YARN-721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
PengZhang updated YARN-721:
---------------------------
Description:
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.
was:
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.
> 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
>
> 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