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

Sharad Agarwal updated MAPREDUCE-817:
-------------------------------------

    Attachment: 817_v1.patch

This patch;
- Adds the getHistoryFile() api to JobStatus
- As soon as the job history file is moved to HDFS, the entire job 
datastructures are removed from the memory, barring JobStatus object. JobStatus 
objects are kept in RetiredJobs cache with default cache size 0f 5000.
- Retired jobs table is added to the Jobtracker UI, which will show the last 
100 jobs in reverse "finish time" order. Perhaps later we can add the 
pagination to show more jobs. The job id links to the Job history page for that 
job. 
- On accessing the job history file via UI, the history info is loaded and put 
in the LRU cache, default size being 5.
- The "Completed" and "Failed" tables will show up in the UI only if there are 
jobs which have completed but not yet "Retired".

> Add a JobClient API to get job history file url
> -----------------------------------------------
>
>                 Key: MAPREDUCE-817
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-817
>             Project: Hadoop Map/Reduce
>          Issue Type: New Feature
>          Components: client, jobtracker
>            Reporter: Sharad Agarwal
>            Assignee: Sharad Agarwal
>         Attachments: 817_v1.patch
>
>
> MAPREDUCE-814 will provide a way to keep the job history files in HDFS. There 
> should be a way to get the url for the completed job history fie.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to