You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2013/10/14 20:48:42 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=13794361#comment-13794361 ]
Hudson commented on MAPREDUCE-5546:
-----------------------------------
SUCCESS: Integrated in Hadoop-trunk-Commit #4600 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/4600/])
MAPREDUCE-5546. mapred.cmd on Windows set HADOOP_OPTS incorrectly. Contributed by Chuan Liu. (cnauroth: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1532016)
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/trunk/hadoop-mapreduce-project/bin/mapred.cmd
> 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)