Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
2.0.2-alpha
-
None
-
Reviewed
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.