You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-user@hadoop.apache.org by "Habermaas, William" <Wi...@fatwire.com> on 2009/02/05 17:32:40 UTC

Connect to namenode

After creation and startup of the hadoop namenode, you can only connect
to the namenode via hostname and not IP.

 

EX. hostname for box is sunsystem07, ip is 10.120.16.99

 

If you use the following url, "hdfs://10.120.16.99", to connect to the
namenode, the following message will be printed:

   Wrong FS: hdfs://10.120.16.99:9000/, expected:
hdfs://sunsystem07:9000

You will only be able to connect successfully if
"hdfs://sunsystem07:9000" is used.

 

It seems reasonable to allow connection either by IP or name.   Is there
a reason for this behavior or is it a bug?

Re: Connect to namenode

Posted by Raghu Angadi <ra...@yahoo-inc.com>.

I don't think it is intentional. Please file a jira with all the details 
about how to reproduce (with actual configuration files).

thanks,
Raghu.

Habermaas, William wrote:
> After creation and startup of the hadoop namenode, you can only connect
> to the namenode via hostname and not IP.
> 
>  
> 
> EX. hostname for box is sunsystem07, ip is 10.120.16.99
> 
>  
> 
> If you use the following url, "hdfs://10.120.16.99", to connect to the
> namenode, the following message will be printed:
> 
>    Wrong FS: hdfs://10.120.16.99:9000/, expected:
> hdfs://sunsystem07:9000
> 
> You will only be able to connect successfully if
> "hdfs://sunsystem07:9000" is used.
> 
>  
> 
> It seems reasonable to allow connection either by IP or name.   Is there
> a reason for this behavior or is it a bug?
> 
>  
> 
>