[
https://issues.apache.org/jira/browse/MAPREDUCE-2644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13063971#comment-13063971
]
Hadoop QA commented on MAPREDUCE-2644:
--------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12485459/MAPREDUCE-2644.patch
against trunk revision 1145424.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
-1 patch. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/453//console
This message is automatically generated.
> 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
