-
Type:
Bug
-
Status: Resolved
-
Priority:
Critical
-
Resolution: Fixed
-
Affects Version/s: 0.21.0, 0.22.0
-
Fix Version/s: 0.20.203.0
-
Component/s: jobtracker
-
Labels:None
-
Release Note:
Today all the jobhistory files are dumped in one job-history folder. This can cause problems when there is a need to search the history folder (job-recovery etc). It would be nice if we group all the jobs under a user folder. So all the jobs for user amar will go in history-folder/amar/. Jobs can be categorized using various features like jobid, date, jobname etc but using username will make the search much more efficient and also will not result into namespace explosion.
- blocks
-
MAPREDUCE-1988 We would like more information to be available in job history index
-
- Resolved
-
- incorporates
-
HADOOP-4934 Distinguish running/successful/failed/killed jobs in jobtracker's history
-
- Closed
-
- is blocked by
-
MAPREDUCE-70 Unify the way job history filename is parsed
-
- Resolved
-
- is depended upon by
-
MAPREDUCE-1941 Need a servlet in JobTracker to stream contents of the job history file
-
- Resolved
-
- is related to
-
MAPREDUCE-1978 [Rumen] TraceBuilder should provide recursive input folder scanning
-
- Closed
-
- requires
-
MAPREDUCE-2032 TestJobOutputCommitter fails in ant test run
-
- Closed
-