[
https://issues.apache.org/jira/browse/HADOOP-1202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487155
]
Michael Bieniosek commented on HADOOP-1202:
-------------------------------------------
> How do expect cluster to work well when config is inconsistent? Config is the
> only way for datanode to find where namenode is located. Binding to 0.0.0.0
> does not fix misconfiguration.
My problem is that my namenode and jobtracker have more than one name, because
of the way the firewall is set up. Internally, it listens on interface 1,
where it can talk to the datanodes and tasktrackers, while externally it
listens on interface 2, where it can talk to the rest of the network. The
namenode/jobtracker need to listen on both interfaces, which happen to have
different dns names and different ips.
> Need to be able to set jobtracker & namenode to bind to 0.0.0.0
> ---------------------------------------------------------------
>
> 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
>
>
> 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.
