Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <1995290091.1216404631976.JavaMail.jira@brutus>
Date: Fri, 18 Jul 2008 11:10:31 -0700 (PDT)
From: "Ari Rabkin (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Updated: (HADOOP-3772) Proposed hadoop instrumentation API
In-Reply-To: <2129610118.1216228831691.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HADOOP-3772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ari Rabkin updated HADOOP-3772:
-------------------------------

    Attachment: instrumentation-2.patch

add JobTracker instrumentation, document options in hadoop-default.xml

> 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
>         Attachments: instrumentation-2.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.