[MAPREDUCE-1505] Cluster class should create the rpc client only when needed

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.20.2
• Fix Version/s: 0.22.0
• Component/s: client
• Hadoop Flags: Reviewed
• Release Note: Lazily construct a connection to the JobTracker from the job-submission client.
• Assignee: Dick King
• Reporter: Devaraj Das
• Created: 18/Feb/10 21:56
• Updated: 12/Dec/11 06:19
• Resolved: 06/Jun/10 01:28

Description

It will be good to have the org.apache.hadoop.mapreduce.Cluster create the rpc client object only when needed (when a call to the jobtracker is actually required). org.apache.hadoop.mapreduce.Job constructs the Cluster object internally and in many cases the application that created the Job object really wants to look at the configuration only. It'd help to not have these connections to the jobtracker especially when Job is used in the tasks (for e.g., Pig calls mapreduce.FileInputFormat.setInputPath in the tasks and that requires a Job object to be passed).

In Hadoop 20, the Job object internally creates the JobClient object, and the same argument applies there too.

Issue Links

• is depended upon by: MAPREDUCE-118 Job.getJobID() will always return null