ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mahadev konar (JIRA)" <>
Subject [jira] [Commented] (AMBARI-2219) HDFS install results in Invalid hostname exception during namenode start
Date Thu, 30 May 2013 05:17:20 GMT


Mahadev konar commented on AMBARI-2219:

 Looks like this is mostly because a config is getting set to null ( in core-site.xml.
You might want to look at the configuration object via the api and see what are the various
key/val's in the configs.
> HDFS install results in Invalid hostname exception during namenode start
> ------------------------------------------------------------------------
>                 Key: AMBARI-2219
>                 URL:
>             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 (in the pop-up
dialog on the UI under the namenode start task)
> 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:

View raw message