[jira] [Commented] (MAPREDUCE-2644) NodeManager fails to create containers when NM_LOG_DIR is not explicitly set in the Configuration

["Aaron T. Myers (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MAPREDUCE-2644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13060233#comment-13060233 ] 

Aaron T. Myers commented on MAPREDUCE-2644:
-------------------------------------------

Hey Josh, the usual thing done in the rest of the Hadoop code when providing a default value for a config is to use the two-argument version of {{Configuration.get(...)}} whose first argument is the config key and whose second argument will be returned as the value if no value for that key is set in the conf object.

> 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