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

["Fredrik Hedberg (JIRA)" <ji...@apache.org>]

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

Fredrik Hedberg updated HADOOP-1202:
------------------------------------

    Attachment: bind-all-addresses-2.patch

Michael's patch updated to apply to trunk.

> 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-2.patch, 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.