hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Srinivas (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-9625) HADOOP_OPTS not picked up by hadoop command
Date Thu, 06 Jun 2013 06:12:20 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-9625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13676743#comment-13676743

Suresh Srinivas commented on HADOOP-9625:

Paul, you need to rebase this patch. In the patch the following line no longer has HADOOP_CLIENT_OPTS
in the latest code on trunk any more.

- export HADOOP_OPTS="-Djava.net.preferIPv4Stack=true $HADOOP_CLIENT_OPTS"

> HADOOP_OPTS not picked up by hadoop command
> -------------------------------------------
>                 Key: HADOOP-9625
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9625
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: bin, conf
>    Affects Versions: 2.0.3-alpha, 2.0.4-alpha
>            Reporter: Paul Han
>            Priority: Minor
>             Fix For: 2.0.5-alpha
>         Attachments: HADOOP-9625.patch, HADOOP-9625-release-2.0.5-alpha-rc2.patch
>   Original Estimate: 12h
>  Remaining Estimate: 12h
> When migrating from hadoop 1 to hadoop 2, one thing caused our users grief are those
non-backward-compatible changes. This JIRA is to fix one of those changes:
>   HADOOP_OPTS is not picked up any more by hadoop command
> With Hadoop 1, HADOOP_OPTS will be picked up by hadoop command. With Hadoop 2, HADOOP_OPTS
will be overwritten by the line in conf/hadoop_env.sh :
> export HADOOP_OPTS="-Djava.net.preferIPv4Stack=true"
> We should fix this.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message