hadoop-hdfs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron T. Myers" <...@cloudera.com>
Subject Re: Binding NameNode to another address
Date Wed, 30 Nov 2011 18:12:36 GMT
Hi David,

You should file a JIRA with a description of the issue and attach the patch
here: https://issues.apache.org/jira/browse/HDFS

We can discuss the issue in detail and the merits of the patch over there.

--
Aaron T. Myers
Software Engineer, Cloudera



On Tue, Nov 29, 2011 at 8:37 PM, David Robson <David.Robson@quest.com>wrote:

>  Hi,****
>
> ** **
>
> Does anyone know anything about the dfs.namenode.rpc-address parameter? I
> posted the below to the hdfs-user list but thought I might get a better
> response from the dev list.****
>
> ** **
>
> David****
>
> ** **
>
> *From:* David Robson [mailto:David.Robson@quest.com]
> *Sent:* Friday, 25 November 2011 3:59 PM
> *To:* hdfs-user@hadoop.apache.org
> *Subject:* Binding NameNode to another address****
>
> ** **
>
> Hi,****
>
> ** **
>
> If I set the fs.default.name to hdfs://hostname.domain:8020 this will
> bind to the address associated with that hostname. I have multiple network
> interfaces so would like it to bind to 0.0.0.0.****
>
> ** **
>
> It looks like the property dfs.namenode.rpc-address was intended to be
> used for this purpose – but doesn’t look like it was implemented.****
>
> ** **
>
> I have changed the code as in the following patch (against the trunk) and
> it seems to fix the issue but I’m not sure if this is OK. I also tried
> looking for JIRA entries but there seem to be a lot related to this so
> wasn’t sure if I should post this to one of them or create a new one?****
>
> ** **
>
> Can somebody please have a look at the patch and advise what I should do?*
> ***
>
> ** **
>
> Thanks,****
>
> ** **
>
> David****
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message