hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Devaraj Das (JIRA)" <j...@apache.org>
Subject [jira] Updated: (MAPREDUCE-1505) Cluster class should create the rpc client only when needed
Date Thu, 18 Feb 2010 21:59:27 GMT

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

Devaraj Das updated MAPREDUCE-1505:
-----------------------------------

    Summary: Cluster class should create the rpc client only when needed  (was: Job class
should create the rpc client only when needed)

> 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
>
>
> 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.


Mime
View raw message