[
https://issues.apache.org/jira/browse/HADOOP-1202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487161
]
Raghu Angadi commented on HADOOP-1202:
--------------------------------------
I do think it will be useful to be able to bind to all interfaces, at least in
some special cases.
Just out of curiosity, in your set up what is in 'rest of the network' that
needs to talk to namenode?. I think I still don't follow your set up.
> 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.
