[HADOOP-1202] Jobtracker & Namenode can only bind to one interface

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Assignee: Unassigned
• Reporter: Michael Bieniosek
• Created: 04/Apr/07 17:24
• Updated: 02/May/13 02:29

Description

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.

Issue Links

• is depended upon by: HADOOP-1638 Master node unable to bind to DNS hostname
• is related to: HADOOP-1265 TaskTracker won't bind to localhost