[
https://issues.apache.org/jira/browse/MAPREDUCE-5933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Kanter updated MAPREDUCE-5933:
-------------------------------------
Attachment: MAPREDUCE-5933.patch
{quote}5. The countersToJSON method already turns the Counters into JSON so the
ATS can display them.
Yeah, my question is whether we really want to make counters' details
visualization-friendly via timeline read APIs, while the JHS will query this
data, reconstruct counter objects and show them there. If we don't, the easiest
way is to write counters into bytes when storing, and recover them from bytes
when retrieving in.{quote}
The problem with writing them as bytes is that the ATS doesn't know anything
about Counters. It would have to know how to read them back and then convert
them to JSON for display. The way I have it now, the ATS doesn't have to know
anything extra.
{quote}It seems that you published all the events related to job summary, which
may not be enough....{quote}
In the new patch, I've added another method which processes the remaining event
types that were missing. I've also verified that they show up in the ATS
output for a job.
> Enable MR AM to post history events to the timeline server
> ----------------------------------------------------------
>
> Key: MAPREDUCE-5933
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5933
> Project: Hadoop Map/Reduce
> Issue Type: Sub-task
> Components: mr-am
> Reporter: Zhijie Shen
> Assignee: Robert Kanter
> Attachments: MAPREDUCE-5933.patch, MAPREDUCE-5933.patch,
> MAPREDUCE-5933.patch, MAPREDUCE-5933.patch, mr_timelineserver_response.txt
>
>
> Nowadays, MR AM collects the history events and writes it to HDFS for JHS to
> source. With the timeline server, MR AM can put these events there.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
