[
https://issues.apache.org/jira/browse/YARN-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13577128#comment-13577128
]
Zhijie Shen commented on YARN-389:
----------------------------------
{quote}
Zhijie, what is your setting for yarn.scheduler.maximum-allocation-mb? That is
the configs that should reject allocations that aren't satisfiable.
{quote}
Hi Vinod, I set yarn.scheduler.maximum-allocation-mb <=
yarn.nodemanager.resource.memory-mb (single node cluster). However, the
requested resource wasn't bounded by yarn.scheduler.maximum-allocation-mb. On
the other side, I saw the code to set amMemory to maxMemory if amMemory >
maxMemory. I need to dig deeper.
> Infinitely assigning containers when the required resource exceeds the
> cluster's absolute capacity
> --------------------------------------------------------------------------------------------------
>
> Key: YARN-389
> URL: https://issues.apache.org/jira/browse/YARN-389
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Zhijie Shen
> Assignee: Zhijie Shen
>
> I've run wordcount example on branch-2 and trunk. I've set
> yarn.nodemanager.resource.memory-mb to 1G and
> yarn.app.mapreduce.am.resource.mb to 1.5G. Therefore, resourcemanager is to
> assign a 2G AM container for AM. However, the nodemanager doesn't have enough
> memory to assign the container. The problem is that the assignment operation
> will be repeated infinitely, if the assignment cannot be accomplished. Logs
> follow.
--
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
