hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arun C Murthy (JIRA)" <j...@apache.org>
Subject [jira] Updated: (MAPREDUCE-1505) Cluster class should create the rpc client only when needed
Date Tue, 13 Apr 2010 21:31:54 GMT

     [ https://issues.apache.org/jira/browse/MAPREDUCE-1505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Arun C Murthy updated MAPREDUCE-1505:

    Release Note: Lazily construct a connection to the JobTracker from the job-submission

> 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
>             Fix For: 0.22.0
>         Attachments: 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.
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message