hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sandy Ryza (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-4994) Can't submit local job with hadoop jar -jt local
Date Fri, 08 Feb 2013 20:41:14 GMT

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

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

On closer examination, Cluster#initialize doesn't need any special handling, mapreduce.framework.name
should be set to local.
                
> Can't submit local job with hadoop jar -jt local
> ------------------------------------------------
>
>                 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
>
> 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.
> 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