hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alejandro Abdelnur (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-4994) -jt generic command line option does not work
Date Wed, 13 Feb 2013 19:34:13 GMT

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

Alejandro Abdelnur commented on MAPREDUCE-4994:
-----------------------------------------------

Mmhh, wouldn't be better to get 1 MAP as default if not set?
                
> -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
>             Fix For: 2.0.4-beta
>
>         Attachments: MAPREDUCE-4994-1.patch, MAPREDUCE-4994-addendum.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

Mime
View raw message