[
https://issues.apache.org/jira/browse/MAPREDUCE-679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Douglas updated MAPREDUCE-679:
------------------------------------
Status: Open (was: Patch Available)
* This adds {{generateRetiredJobXml}} to JSPUtil to use the package-private
"mechanism" for obtaining retired jobs from {{generateRetiredJobTable}}, right?
I suppose it's unfair to hold this to a higher standard than the tracker page,
but building a buffer of up to 100 jobs in XML before writing it out is not
ideal. Could this be a little more sparing of memory by passing the Writer to
the utility function?
* It may not matter given the preceding, but StringBuilder is preferred over
StringBuffer in a single-threaded context
* This should use a real XML writer instead of writing the tags as string
literals. xmlenc is used in some of the existing code. It might be better-
since the data are all key=value pairs not nested structures- if these were
expressed less verbosely. On reflection, wouldn't it make sense to just let
each item in a {{<%s_jobs>}} be a {{job}} instead of a {{%s_job}}? e.g.
{noformat}
<running_jobs>
<job jobid="job_xxx_0003" user="fuser" name="word count" map_complete="8" ...>
<job jobid="job_xxx_0005" user="faser" name="word count" map_complete="6" ...>
</running_jobs>
{noformat}
> XML-based metrics as JSP servlet for JobTracker
> -----------------------------------------------
>
> Key: MAPREDUCE-679
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-679
> Project: Hadoop Map/Reduce
> Issue Type: New Feature
> Components: jobtracker
> Reporter: Aaron Kimball
> Assignee: Aaron Kimball
> Attachments: example-jobtracker-completed-job.xml,
> example-jobtracker-running-job.xml, MAPREDUCE-679.2.patch,
> MAPREDUCE-679.3.patch, MAPREDUCE-679.4.patch, MAPREDUCE-679.5.patch,
> MAPREDUCE-679.patch
>
>
> In HADOOP-4559, a general REST API for reporting metrics was proposed but
> work seems to have stalled. In the interim, we have a simple XML translation
> of the existing JobTracker status page which provides the same metrics
> (including the tables of running/completed/failed jobs) as the human-readable
> page. This is a relatively lightweight addition to provide some
> machine-understandable metrics reporting.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
