hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Kimball (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HDFS-1288) start-all.sh / stop-all.sh does not seem to work with HDFS
Date Thu, 08 Jul 2010 18:47:53 GMT

    [ https://issues.apache.org/jira/browse/HDFS-1288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12886405#action_12886405
] 

Aaron Kimball commented on HDFS-1288:
-------------------------------------

If I explicitly set $HADOOP_HDFS_HOME=$HADOOP_HOME/hdfs then it works fine. But what is curious
is that I do not need to explicitly set $HADOOP_MAPRED_HOME.

So there's some asymmetry in how these scripts work with HDFS and mapred. At the very least,
they should print a warning that they couldn't do the dfs-side work if they can't find the
scripts?


> start-all.sh / stop-all.sh does not seem to work with HDFS
> ----------------------------------------------------------
>
>                 Key: HDFS-1288
>                 URL: https://issues.apache.org/jira/browse/HDFS-1288
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: scripts
>    Affects Versions: 0.21.0
>            Reporter: Aaron Kimball
>            Priority: Minor
>
> The start-all.sh / stop-all.sh script shipping with the "combined" hadoop-0.21.0-rc1
does not start/stop the DFS daemons unless $HADOOP_HDFS_HOME is explicitly set.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message