You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Trevor McKay (JIRA)" <ji...@apache.org> on 2013/05/29 20:52:23 UTC

[jira] [Commented] (AMBARI-2219) HDFS install results in Invalid hostname exception during namenode start

    [ https://issues.apache.org/jira/browse/AMBARI-2219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13669569#comment-13669569 ] 

Trevor McKay commented on AMBARI-2219:
--------------------------------------

Not sure if this is a hadoop issue or an ambari issue, or if others can reproduce it.

Steps to reproduce are simply:

1) Set up a clean RHEL 6.2 or 6.3 agent machine
2) Build snapshot rpms from the ambari trunk
3) Run the cluster install wizard and select HDFS and MAPREDUCE for the agent
                
> HDFS install results in Invalid hostname exception during namenode start
> ------------------------------------------------------------------------
>
>                 Key: AMBARI-2219
>                 URL: https://issues.apache.org/jira/browse/AMBARI-2219
>             Project: Ambari
>          Issue Type: Bug
>          Components: agent, controller
>    Affects Versions: 1.3.0
>         Environment: Fedora 16 server
> RHEL 6.2 or 6.3 agent
> Installing a single machine cluster with HDFS and mapreduce
>            Reporter: Trevor McKay
>         Attachments: hadoop-hdfs-namenode-somemachine.log
>
>
> Very reproducible for me, using snapshot builds of trunk and freshly provisioned agent machines (reusing the same server after ambari-reset)
> The HDFS install/start/test fails on starting the namenode with this error:
> notice: /Stage[2]/Hdp-hadoop::Namenode/Hdp-hadoop::Namenode::Create_app_directories[create_app_directories]/Hdp-hadoop::Hdfs::Directory[/mapred]/Hdp-hadoop::Exec-hadoop[fs -mkdir /mapred]/Hdp::Exec[hadoop --config /etc/hadoop/conf fs -mkdir /mapred]/Exec[hadoop --config /etc/hadoop/conf fs -mkdir /mapred]/returns: 13/05/29 13:14:54 WARN fs.FileSystem: "null" is a deprecated filesystem name. Use "hdfs://null/" instead.
> Is this a configuration error?  Something wrong in the agent?  Something erroneous sent from the server?

--
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