[ http://issues.apache.org/jira/browse/HADOOP-132?page=all ]

David Bowen updated HADOOP-132:
-------------------------------

    Attachment: javadoc.tgz

Here is an updated API, incorporating the feedback I've received so far.  The 
main
changes are 

   (1) Ganglia support is included - this doesn't really affect the API, but 
the javadoc describes the configuration options which might be of interest.

   (2) The SPI (service provider interface) is now in a separate package, and 
it does most of the implementation work so that implementation packages (like 
the file and ganglia sub-packages) can be quite small.

  (3) The unbuffered option has been removed.  This means that developers can 
use the API freely in inner-loops without the concern that metric reporting 
might be configured to emit data on every update.  The data will just be stored 
in an internal table, and the table will only be sent periodically to the 
metrics server.



> An API for reporting performance metrics
> ----------------------------------------
>
>          Key: HADOOP-132
>          URL: http://issues.apache.org/jira/browse/HADOOP-132
>      Project: Hadoop
>         Type: New Feature

>     Reporter: David Bowen
>  Attachments: javadoc.tgz, javadoc.tgz
>
> I'd like to propose adding an API for reporting performance metrics.  I will 
> post some javadoc as soon as I figure out how to do so.  The idea is for the 
> API to be sufficiently abstract that various different implementations can be 
> plugged in.  In particular, there would be one that just writes the metric 
> data to a file, and another that sends metrics to Ganglia.  It would also be 
> possible to plug in an implementation that can support high-frequency (say, 
> per-second) sending of fairly large amounts of data (up to hundreds of 
> metrics) across the network.
> I'd be very interested in people's thoughts about what the requirements 
> should be for such an API.
> - David Bowen

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

Reply via email to