[
https://issues.apache.org/jira/browse/MAPREDUCE-817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sharad Agarwal updated MAPREDUCE-817:
-------------------------------------
Release Note:
Provides a way to configure the cache of JobStatus objects for the retired
jobs.
Adds an API in RunningJob to access history file url.
Adds a LRU based cache for job history files loaded in memory when accessed via
JobTracker web UI.
Adds Retired Jobs table on the Jobtracker UI. The job move from Running to
Completed/Failed table. Then job move to Retired table when it is purged from
memory. The Retired table shows last 100 retired jobs. The Completed/Failed
jobs table are only shown if there are non-zero jobs in the table.
was:Provides a way to configure the cache of JobStatus objects for the
retired jobs. Adds an API in RunningJob to access history file url. Adds a LRU
based cache for job history files loaded in memory when accessed via JobTracker
web UI.
> Add a cache for retired jobs with minimal job info and provide a way to
> access history file url
> -----------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-817
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-817
> Project: Hadoop Map/Reduce
> Issue Type: Sub-task
> Components: client, jobtracker
> Reporter: Sharad Agarwal
> Assignee: Sharad Agarwal
> Fix For: 0.21.0
>
> Attachments: 817_v1.patch, 817_v2.patch, 817_v3.patch,
> 817_ydist.patch, 817_ydist_new.patch, 817_ydist_new_1.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. The
> completed jobs can be purged from memory more aggressively from jobtracker
> since the clients can retrieve the information from history file. Jobtracker
> can just maintain the very basic info about the completed jobs.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
