Details
-
Sub-task
-
Status: Closed
-
Major
-
Resolution: Fixed
-
0.20.1
-
None
-
None
-
Incompatible change, Reviewed
-
Description
Currently, parsing the job history logs with external tools is very difficult because of the format. The most critical problem is that newlines aren't escaped in the strings. That makes using tools like grep, sed, and awk very tricky.
Attachments
Attachments
Issue Links
- blocks
-
MAPREDUCE-864 Enhance JobClient API implementations to look at history files to get information about jobs that are not in memory
- Resolved
-
MAPREDUCE-975 Add an API in job client to get the history file url for a given job id
- Closed
-
MAPREDUCE-198 Log job history events to a common dump file
- Resolved
-
MAPREDUCE-980 Modify JobHistory to use Avro for serialization instead of raw JSON
- Closed
-
MAPREDUCE-277 Job history counters should be avaible on the UI.
- Closed
- incorporates
-
MAPREDUCE-881 Jobtracker continues even if History initialization fails
- Resolved
-
MAPREDUCE-926 History viewer on web UI should filter by job-id also
- Resolved
- relates to
-
MAPREDUCE-2251 Remove mapreduce.job.userhistorylocation config
- Closed