You are viewing a plain text version of this content. The canonical link for it is here.

Posted to mapreduce-issues@hadoop.apache.org by "Sandy Ryza (JIRA)" <ji...@apache.org> on 2013/02/09 02:16:11 UTC

[jira] [Commented] (MAPREDUCE-4994) -jt generic command line option does not work

    [ https://issues.apache.org/jira/browse/MAPREDUCE-4994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13575021#comment-13575021 ] 

Sandy Ryza commented on MAPREDUCE-4994:
---------------------------------------

Updated patch to not set the number of local mappers to 1.  Verified via command line that it works both with local and remote. 
                
> -jt generic command line option does not work
> ---------------------------------------------
>
>                 Key: MAPREDUCE-4994
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4994
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 2.0.2-alpha
>            Reporter: Sandy Ryza
>            Assignee: Sandy Ryza
>         Attachments: MAPREDUCE-4994-1.patch, MAPREDUCE-4994.patch
>
>
> hadoop jar myjar.jar MyDriver -fs file:/// -jt local input.txt output/
> should run a job using the local file system and the local job runner. Instead it tries to connect to a jobtracker.
> hadoop jar myjar.jar MyDriver -fs file:/// -jt host:port input.txt output/
> does not use the given host/port
> This appears to be because Cluster#initialize, which loads the ClientProtocol, contains no special handling for mapred.job.tracker.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira