[
https://issues.apache.org/jira/browse/HADOOP-1202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487139
]
Raghu Angadi commented on HADOOP-1202:
--------------------------------------
> The datanodes get very confused if the dns name they have configured for the
> namenode is not exactly the same as the name the namenode is configured with.
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.
But I think it will be useful to be able to specify bind address. I think the
default value for bind address should be "default" which would imply what we do
now. Most users will never need to look at it. On some special clusters it
could be set to desired value.
> 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.
