[
https://issues.apache.org/jira/browse/YARN-55?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Shah resolved YARN-55.
-----------------------------
Resolution: Invalid
Closing this as invalid.
If an AM requests more memory than the configured maximum memory for the RM
Scheduler, RM will throw an error.
If there are no live nodes capable of handling the memory asked for, that
should be looked at in YARN-56.
> YARN needs to properly check the NM,AM memory properties in yarn-site.xml and
> mapred.xml and report errors accordingly.
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: YARN-55
> URL: https://issues.apache.org/jira/browse/YARN-55
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager
> Affects Versions: 2.0.2-alpha, 0.23.3
> Environment: CentOs6.0, Hadoop2.0.0 Alpha
> Reporter: Anil Gupta
> Labels: Map, Reduce, YARN
>
> Please refer to this discussion on the Hadoop Mailing list:
> http://comments.gmane.org/gmane.comp.jakarta.lucene.hadoop.user/33110
> Summary:
> I was running YARN(Hadoop2.0.0 Alpha) on a 8 datanode, 4 admin node
> Hadoop/HBase cluster. My datanodes were only having 3.2GB of memory. So, i
> configured the yarn.nodemanager.resource.memory-mb property in yarn-site.xml
> to 1200. After setting the property if i run any Yarn Job then the
> NodemManager wont be able to start any Map task since by default the
> yarn.app.mapreduce.am.resource.mb property is set to 1500 MB in
> mapred-site.xml.
> Expected Behavior: NodeManager should give an error if
> yarn.app.mapreduce.am.resource.mb >= yarn.nodemanager.resource.memory-mb.
> Please let me know if more information is required.
--
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
