[MAPREDUCE-291] Optionally a separate daemon should serve JobHistory - ASF JIRA

XML

Word

Printable

JSON

Details

Type: Improvement
Status: Resolved
Priority: Major
Resolution: Fixed
Affects Version/s: None
Fix Version/s: None
Component/s: jobtracker
Labels:
None

Description

Currently the JobTracker serves the JobHistory to end-users off files local-disk/hdfs. While running very large clusters with a large user-base might result in lots of traffic for job-history which needlessly taxes the JobTracker. The proposal is to have an optional daemon which handles serving of job-history requests.

Attachments

- Sort By Name
- Sort By Date
- Ascending
- Descending

HADOOP-5083-v1.2.patch
22/Jan/09 09:09
114 kB
Amar Kamat
HADOOP-5083-v1.9.patch
28/Jan/09 18:04
142 kB
Amar Kamat
HADOOP-5083-v1.9.4.patch
30/Jan/09 13:58
145 kB
Amar Kamat
HADOOP-5083-v1.11.4.patch
10/Feb/09 06:48
148 kB
Amar Kamat
HADOOP-5083-v1.11.5.patch
10/Feb/09 12:22
148 kB
Amar Kamat
HADOOP-5083-v1.11.9.patch
19/Feb/09 11:23
155 kB
Amar Kamat
HADOOP-5083-v1.11.11.patch
24/Feb/09 11:37
153 kB
Amar Kamat

Issue Links

is depended upon by

MAPREDUCE-1941 Need a servlet in JobTracker to stream contents of the job history file

Resolved

is part of

MAPREDUCE-331 Make jobtracker resilient to memory issues

Resolved

relates to

MAPREDUCE-177 Hadoop performance degrades significantly as more and more jobs complete

Resolved

Activity

People

Assignee:: Amar Kamat

Reporter:: Arun Murthy

Votes:: 0 Vote for this issue

Watchers:: 13 Start watching this issue

Dates

Created:: 20/Jan/09 09:28

Updated:: 21/Jul/14 18:13

Resolved:: 21/Jul/14 18:13