You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "Roman Shaposhnik (JIRA)" <ji...@apache.org> on 2011/09/22 02:23:26 UTC

[jira] [Created] (BIGTOP-104) hadoop daemons can not be started because hadoop-config.sh resets HADOOP_HOME

hadoop daemons can not be started because hadoop-config.sh resets HADOOP_HOME
-----------------------------------------------------------------------------

                 Key: BIGTOP-104
                 URL: https://issues.apache.org/jira/browse/BIGTOP-104
             Project: Bigtop
          Issue Type: Bug
          Components: General
    Affects Versions: 0.1.0
            Reporter: Roman Shaposhnik
            Assignee: Roman Shaposhnik
             Fix For: 0.2.0


The HADOOP_HOME variable gets clobbered and ends up pointing to /etc

# the root of the Hadoop installation
export HADOOP_HOME=`dirname "$this"`/..


--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (BIGTOP-104) hadoop daemons can not be started because hadoop-config.sh resets HADOOP_HOME

Posted by "Roman Shaposhnik (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/BIGTOP-104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13112259#comment-13112259 ] 

Roman Shaposhnik commented on BIGTOP-104:
-----------------------------------------

This is a really, really, really bad behvaiour of hadoop-config.sh. However since we can't really patch 0.20.2 we have to workaround in our daemon management scripts

> hadoop daemons can not be started because hadoop-config.sh resets HADOOP_HOME
> -----------------------------------------------------------------------------
>
>                 Key: BIGTOP-104
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-104
>             Project: Bigtop
>          Issue Type: Bug
>          Components: General
>    Affects Versions: 0.1.0
>            Reporter: Roman Shaposhnik
>            Assignee: Roman Shaposhnik
>             Fix For: 0.2.0
>
>
> The HADOOP_HOME variable gets clobbered and ends up pointing to /etc
> # the root of the Hadoop installation
> export HADOOP_HOME=`dirname "$this"`/..

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (BIGTOP-104) hadoop daemons can not be started because hadoop-config.sh resets HADOOP_HOME

Posted by "Roman Shaposhnik (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/BIGTOP-104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Roman Shaposhnik updated BIGTOP-104:
------------------------------------

    Attachment: BIGTOP-104.patch.txt

> hadoop daemons can not be started because hadoop-config.sh resets HADOOP_HOME
> -----------------------------------------------------------------------------
>
>                 Key: BIGTOP-104
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-104
>             Project: Bigtop
>          Issue Type: Bug
>          Components: General
>    Affects Versions: 0.1.0
>            Reporter: Roman Shaposhnik
>            Assignee: Roman Shaposhnik
>             Fix For: 0.2.0
>
>         Attachments: BIGTOP-104.patch.txt
>
>
> The HADOOP_HOME variable gets clobbered and ends up pointing to /etc
> # the root of the Hadoop installation
> export HADOOP_HOME=`dirname "$this"`/..

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (BIGTOP-104) hadoop daemons can not be started because hadoop-config.sh resets HADOOP_HOME

Posted by "Eli Collins (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/BIGTOP-104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13112270#comment-13112270 ] 

Eli Collins commented on BIGTOP-104:
------------------------------------

Good catch! Please file an upstream jira against Hadoop.

> hadoop daemons can not be started because hadoop-config.sh resets HADOOP_HOME
> -----------------------------------------------------------------------------
>
>                 Key: BIGTOP-104
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-104
>             Project: Bigtop
>          Issue Type: Bug
>          Components: General
>    Affects Versions: 0.1.0
>            Reporter: Roman Shaposhnik
>            Assignee: Roman Shaposhnik
>             Fix For: 0.2.0
>
>         Attachments: BIGTOP-104.patch.txt
>
>
> The HADOOP_HOME variable gets clobbered and ends up pointing to /etc
> # the root of the Hadoop installation
> export HADOOP_HOME=`dirname "$this"`/..

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (BIGTOP-104) hadoop daemons can not be started because hadoop-config.sh resets HADOOP_HOME

Posted by "Bruno Mahé (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/BIGTOP-104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13112266#comment-13112266 ] 

Bruno Mahé commented on BIGTOP-104:
-----------------------------------

+1

> hadoop daemons can not be started because hadoop-config.sh resets HADOOP_HOME
> -----------------------------------------------------------------------------
>
>                 Key: BIGTOP-104
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-104
>             Project: Bigtop
>          Issue Type: Bug
>          Components: General
>    Affects Versions: 0.1.0
>            Reporter: Roman Shaposhnik
>            Assignee: Roman Shaposhnik
>             Fix For: 0.2.0
>
>         Attachments: BIGTOP-104.patch.txt
>
>
> The HADOOP_HOME variable gets clobbered and ends up pointing to /etc
> # the root of the Hadoop installation
> export HADOOP_HOME=`dirname "$this"`/..

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira