hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Bieniosek (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-1202) Need to be able to set jobtracker & namenode to bind to
Date Tue, 17 Apr 2007 23:03:15 GMT

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

Michael Bieniosek commented on HADOOP-1202:

My jobtracker needs to talk to the tasktrackers, and my namenode needs to talk to my datanodes.
 I need to talk to my jobtracker to give it tasks, and I need to talk to my namenode to retrieve
the results of my jobs.

My hadoop cluster lives on a different network than I do, so I can't talk to it directly.
 As a special exception, my jobtracker and namenode have names in both networks, so if I apply
this patch, everyone can talk to them.  Without the patch, hadoop won't let the jobtracker
and namenode talk in both networks.

> Need to be able to set jobtracker & namenode to bind to
> ---------------------------------------------------------------
>                 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 in these fields causes the server to report 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.

View raw message