[jira] Commented: (HADOOP-1202) Jobtracker & Namenode can only bind to one interface

["Raghu Angadi (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HADOOP-1202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491806 ] 

Raghu Angadi commented on HADOOP-1202:
--------------------------------------

bq. ... I need to talk to my namenode to retrieve the results of my jobs. ...

So you need to read some files from HDFS?. ie. you need to be able to talk to a datanode on the same interface that datanode talks to Namenode ( since that is the ip address namenode gives you ). This jira will help you only if you currently can talk to datanodes but not to namenode. Correct?


> Jobtracker & Namenode can only bind to one interface
> ----------------------------------------------------
>
>                 Key: HADOOP-1202
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1202
>             Project: Hadoop
>          Issue Type: Bug
>            Reporter: Michael Bieniosek
>         Attachments: bind-all-addresses.patch
>
>
> There is no way to tell the jobtracker & namenode to listen on more than one interface.  Because of firewall rules etc., my datanodes/tasktrackers and human users live on different networks, and so talk to the jobtracker/namenode on different interfaces.
> Currently, the namenode will bind to the hostname specified in configuration in fs.default.name, and the jobtracker will bind to the hostname in mapred.job.tracker.  These names are also reported to datanode and tasktracker clients.
> Consequently, putting a fqhn in these fields causes the server to only listen on the interface serving that fqhn.  Putting 0.0.0.0 in these fields causes the server to report 0.0.0.0 as its address to clients, which confuses the clients and causes them to fail.

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