hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doug Cutting (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-3437) mapred.job.tracker default value/docs appear out of sync with code
Date Fri, 23 May 2008 17:25:55 GMT

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

Doug Cutting commented on HADOOP-3437:

If mapred.job.tracker=local, then the JobTracker class should not be used, but rather LocalRunner.
 This logic is in JobClient.  There is no corresponding server-side logic, since, when mapred.job.tracker=local,
it is assumed that you are not starting any server daemons.

What do you expect to happen here?

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

View raw message