hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konstantin Shvachko (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-1202) Need to be able to set jobtracker & namenode to bind to
Date Wed, 04 Apr 2007 19:29:32 GMT

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

Konstantin Shvachko commented on HADOOP-1202:

-1 on introducing a new configuration parameter having the same meaning as the previous one.
You are trying to separate input and output configuration parameters.
We should NOT use config parameters as an output of any function.
I think this is a confusion with the 0 port introduced in HADOOP-1085.
I would rather write 2 different constructors for the NameNode.
One will be used in tests with MiniDFSCluster, which would always poll the port,
or even better if the MiniClusters polls, and just passes the correct address into the NameNode
Another constructor is for a regular name-node startup just as it was before 1085.
I think this a cleaner an less confusing approach.
Same for the JobTracker.

> 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