[
https://issues.apache.org/jira/browse/MAPREDUCE-1505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dick King updated MAPREDUCE-1505:
---------------------------------
Attachment: mapreduce-1505--2010-05-19.patch
Delays making a connection to the job tracker node until it's needed.
Provides a new API so a user can tell whether this has been done, for a given
job [although usually there would be no need to know].
> Cluster class should create the rpc client only when needed
> -----------------------------------------------------------
>
> Key: MAPREDUCE-1505
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1505
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: client
> Affects Versions: 0.20.2
> Reporter: Devaraj Das
> Assignee: Dick King
> Fix For: 0.22.0
>
> Attachments: mapreduce-1505--2010-05-19.patch,
> MAPREDUCE-1505_yhadoop20.patch, MAPREDUCE-1505_yhadoop20_9.patch
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
