You are viewing a plain text version of this content. The canonical link for it is here.

Posted to mapreduce-dev@hadoop.apache.org by "Chris Nauroth (JIRA)" <ji...@apache.org> on 2013/10/14 20:40:42 UTC

[jira] [Resolved] (MAPREDUCE-5546) mapred.cmd on Windows set HADOOP_OPTS incorrectly

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

Chris Nauroth resolved MAPREDUCE-5546.
--------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.2.1
                   3.0.0

I've committed this to trunk, branch-2, and branch-2.2.  Chuan, thank you for the patch.

> mapred.cmd on Windows set HADOOP_OPTS incorrectly
> -------------------------------------------------
>
>                 Key: MAPREDUCE-5546
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5546
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>    Affects Versions: 3.0.0, 2.2.0
>            Reporter: Chuan Liu
>            Assignee: Chuan Liu
>             Fix For: 3.0.0, 2.2.1
>
>         Attachments: MAPREDUCE-5546-trunk.patch
>
>
> The mapred command on Windows does not set HADOOP_OPTS correctly. As a result, some options and settings will miss in the final command, and this will lead to some desired behavior missing. One example is the logging file setting will miss, i.e. even if one set HADOOP_ROOT_LOGGER to DRFA, there is no history server log at HADOOP_LOGFILE.



--
This message was sent by Atlassian JIRA
(v6.1#6144)