[
https://issues.apache.org/jira/browse/HADOOP-3772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12619496#action_12619496
]
Vinod Kumar Vavilapalli commented on HADOOP-3772:
-------------------------------------------------
Seems like errors crept into hadoop-default.xml:
{quote}
<property>
<name>mapred.job.instrumentation</name>
<value>org.apache.hadoop.mapred.JobTrackerMetricsInst</value>
<description>Expert: The instrumentation class to associate with each
TaskTracker.
</description>
</property>
{quote}
The property name should be *mapred.jobtracker.instrumentation*. Also, the
description above should be "[...] class to associate with *the JobTracker*."
> Proposed hadoop instrumentation API
> -----------------------------------
>
> Key: HADOOP-3772
> URL: https://issues.apache.org/jira/browse/HADOOP-3772
> Project: Hadoop Core
> Issue Type: Improvement
> Components: metrics
> Reporter: Ari Rabkin
> Assignee: Ari Rabkin
> Fix For: 0.19.0
>
> Attachments: instrumentation-2.patch, instrumentation-3.patch,
> instrumentation-4.patch, instrumentation.patch
>
>
> We want to evolve the Hadoop metrics subsystem into a more generic
> Instrumentation facility. The ultimate goal is to add structured logging to
> Hadoop, with causal tags, a la X-trace. The existing metrics framework is
> not quite suitable for our needs, since the implementation and interface are
> tightly coupled. There's no way to use the metrics instrumentation points for
> anything other than metricss, and there's no way for a metrics context to
> find out what event just happened.
> We want to tease apart the generic notion of hookable instrumentation points,
> from the specifics of the information recording. The latter ought to be
> pluggable at run-time.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
