hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Erik Forsberg (JIRA)" <j...@apache.org>
Subject [jira] Issue Comment Edited: (HADOOP-3437) mapred.job.tracker default value/docs appear out of sync with code
Date Mon, 15 Jun 2009 19:33:07 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-3437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12719707#action_12719707
] 

Erik Forsberg edited comment on HADOOP-3437 at 6/15/09 12:31 PM:
-----------------------------------------------------------------

Could the problem be IPv6-related? I'm getting this error when trying out the configuration
listed at http://hadoop.apache.org/core/docs/current/quickstart.html#PseudoDistributed

Reading http://www.michael-noll.com/wiki/Running_Hadoop_On_Ubuntu_Linux_(Single-Node_Cluster)#Disabling_IPv6,
I got the idea to explicitly set 127.0.0.1 instead of 0.0.0.0 for values where this was the
default. 

I.e., I replaced 0.0.0.0 with 127.0.0.1 for dfs.secondary.http.address, dfs.datanode.address,
dfs.datanode.http.address, dfs.datanode.ipc.address, dfs.http.address, dfs.datanode.https.address,
dfs.https.address, mapred.job.tracker.http.address, and mapred.task.tracker.http.address.


That solved the problem. 

      was (Author: forsberg):
    Could the problem be IPv6-related? I'm getting this error when trying out the configuration
listed at http://hadoop.apache.org/core/docs/current/quickstart.html#PseudoDistributed

Reading http://wiki.github.com/klbostee/dumbo/short-tutorial, I got the idea to explicitly
set my real IPv4 address instead of 0.0.0.0 for values where this was the default. 

I.e., I replaced 0.0.0.0 with my real IP address for dfs.secondary.http.address, dfs.datanode.address,
dfs.datanode.http.address, dfs.datanode.ipc.address, dfs.http.address, dfs.datanode.https.address,
dfs.https.address, mapred.job.tracker.http.address, and mapred.task.tracker.http.address.
Setting 127.0.0.1 would probably have worked as well. 

That solved the problem. 
  
> mapred.job.tracker default value/docs appear out of sync with code
> ------------------------------------------------------------------
>
>                 Key: HADOOP-3437
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3437
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: conf
>    Affects Versions: 0.18.0
>            Reporter: Steve Loughran
>            Priority: Minor
>
> This is the settings for mapred.job.tracker in SVN_HEAD. If you dont override these,
you get a RuntimeException
> <property>
>   <name>mapred.job.tracker</name>
>   <value>local</value>
>   <description>The host and port that the MapReduce job tracker runs
>   at.  If "local", then jobs are run in-process as a single map
>   and reduce task.
>   </description>
> </property>

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