You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2007/04/04 19:53:32 UTC

[jira] Commented: (HADOOP-1202) Need to be able to set jobtracker & namenode to bind to 0.0.0.0

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

Hadoop QA commented on HADOOP-1202:
-----------------------------------

+1, because http://issues.apache.org/jira/secure/attachment/12354936/bind-all-addresses.patch applied and successfully tested against trunk revision http://svn.apache.org/repos/asf/lucene/hadoop/trunk/525505. Results are at http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch

> 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.