hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Wills (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-2644) NodeManager fails to create containers when NM_LOG_DIR is not explicitly set in the Configuration
Date Tue, 12 Jul 2011 16:08:06 GMT

     [ https://issues.apache.org/jira/browse/MAPREDUCE-2644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Josh Wills updated MAPREDUCE-2644:
----------------------------------

    Status: Patch Available  (was: Open)

> 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

        

Mime
View raw message