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 Tue, 12 Feb 2013 00:55:12 GMT

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

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

Hitesh, you have a point. Still, we have to figure out a meaningful convenience option, something
like '-framework' that could be used doing  '-framework local' or '-framework yarn=HOST:PORT'.
I say convenience because all these options can always be specified as -Dkey=value if you
set all then necessary properties. But I'd say solving this is a complete different JIRA.

This JIRA is is to fix a backwards compatibility issue. Unless there are objection, I'll commit
this tomorrow afternoon PST.



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

Mime
View raw message