Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hadoop-dev@lucene.apache.org
Message-ID: <26177252.1177532175560.JavaMail.jira@brutus>
Date: Wed, 25 Apr 2007 13:16:15 -0700 (PDT)
From: "Jeremy (JIRA)" <jira@apache.org>
To: hadoop-dev@lucene.apache.org
Subject: [jira] Commented: (HADOOP-1202) Need to be able to set jobtracker &
 namenode to bind to 0.0.0.0
In-Reply-To: <12395743.1175707592336.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jeremy commented on HADOOP-1202:
--------------------------------

I agree that there are some configuration issues here that need to be addressed.

In my particular situation, I have had to use IP addresses instead of FQDN's for the properties fs.default.name and mapred.job.tracker.  This is because the server that is running my NameNode and JobTracker is resolving it's FQDN name to 127.0.0.1, and consequently, the services are then being bound to 127.0.0.1 and are not accessible from other machines on the network.

This could be addressed by adjusting the way the FQDN is resolved, however, my hosting provider would have to make that change and in general this seems like something that should be configurable in Hadoop.

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