[
https://issues.apache.org/jira/browse/MAPREDUCE-4994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandy Ryza updated MAPREDUCE-4994:
----------------------------------
Description:
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.
was:
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.
> -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
>
> 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
