hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom White (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-1202) Need to be able to set jobtracker & namenode to bind to 0.0.0.0
Date Wed, 11 Apr 2007 07:11:32 GMT

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

Tom White updated HADOOP-1202:
------------------------------

    Status: Open  (was: Patch Available)

Marking as Open until consensus is reached...

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


Mime
View raw message