[
https://issues.apache.org/jira/browse/MAPREDUCE-2644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13060299#comment-13060299
]
Vinod Kumar Vavilapalli commented on MAPREDUCE-2644:
----------------------------------------------------
Josh, thanks for looking.
Like Aaron mentioned, the correct fix is to mention it in the default files,
but add it in yarn-default.xml instead of mapred-site.xml.
Also just to be sure, you can do the same null-check and set in the base
NodeManager class, that will solve it completely.
> NodeManager fails to create containers when NM_LOG_DIR is not explicitly set
> in the Configuration
> -------------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-2644
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2644
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Reporter: Josh Wills
> Assignee: Josh Wills
> Attachments: MAPREDUCE-2644.patch
>
>
> If the yarn configuration does not explicitly specify a value for the
> yarn.server.nodemanager.log.dir property, container allocation will fail on
> the NodeManager w/an NPE when the LocalDirAllocator goes to create the temp
> directory. In most of the code, we handle this by defaulting to /tmp/logs,
> but we cannot do this in the LocalDirAllocator context, so we need to set the
> default value explicitly in the Configuration.
> Marking this as major b/c it's annoying to bump into it when you're getting
> your first MRv2 cluster up and running. :)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
