[
https://issues.apache.org/jira/browse/MAPREDUCE-864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12754904#action_12754904
]
Sharad Agarwal commented on MAPREDUCE-864:
------------------------------------------
Based on the above comments, instead of job client transparently providing job
information for completed jobs, it will provide a way to get the history url
for a given job id - > MAPREDUCE-975. Clients will use the History apis
directly to construct the information.
> Enhance JobClient API implementations to look at history files to get
> information about jobs that are not in memory
> -------------------------------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-864
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-864
> Project: Hadoop Map/Reduce
> Issue Type: Sub-task
> Components: jobtracker
> Reporter: Devaraj Das
> Assignee: Sharad Agarwal
> Fix For: 0.21.0
>
>
> MAPREDUCE-817 added an API to get the JobHistory URL from the JobTracker.
> This is useful in two ways:
> 1) Users can use this API to get the URL, copy the history files to their
> local disk, and, do processing on them
> 2) APIs like JobSubmissionProtocol.getJobCounters, can read a part of the
> history file, and then return the information to the caller (if the job is
> not there in JT memory). This would mimic most of the
> CompletedJobsStatusStore functionality.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
