[ 
https://issues.apache.org/jira/browse/AVRO-270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12795430#action_12795430
 ] 

Philip Zeyliger commented on AVRO-270:
--------------------------------------

I got a bunch of this working on the airplane yesterday,
but it's sufficiently involved that I'm breaking it out into
a set of related JIRAs.  I won't post them all right away
(because inevitably that takes some time, and I want to make
sure everything is individually tested and what-not), but
here's roughly how it will go:

Stuff that I think works, so will be coming out shortly:

* InProcessTranceiver: For testing (both Avro itself, and code that uses
Avro servers) it's sometimes handy to connect the RPCs without
even a socket.  This implementation of a Transceiver does just that.
(This can, for users, both avoid the overhead of using sockets, and,
in debugging, let users see stack traces that have both client
and server code in one thread.)

* Stopwatch: A simple class that manages elapsed time.

* Histogram/Segmenter: Classes for keeping track of bin counts and summary 
stats.

* Extension of RPCContext to include protocol Methods.

* An RPC Plugin (called StatsPlugin) that, when enabled 
on the tranceiver, keeps track of statistics, and
exposes a servlet for accessing them.  Server-side only.

Stuff that would happen afterwards...

* Make the stats collection work for both clients and server.

* Expose more RPC information (hostnames, etc.) in RPC Context.
Possibly this means having Transcievers be a factory for RPCContext subclasses,
or possibly more/different hooks.

* Expose configurable pivot-like view of statistics.  Granularity could be 
per-host
or per-method or per-(host,method), whatever.

* Re-visiting the concurrency performance implications of the StatsPlugin.

> Expose (optionally) RPC server and client statistics to users
> -------------------------------------------------------------
>
>                 Key: AVRO-270
>                 URL: https://issues.apache.org/jira/browse/AVRO-270
>             Project: Avro
>          Issue Type: New Feature
>          Components: java
>            Reporter: Philip Zeyliger
>            Assignee: Philip Zeyliger
>
> When working with a live systme, it's often quite handy to see what RPCs it's 
> processing, how long they take, which ones are in flight, etc.  I hope for 
> this to be lightweight enough that it's always on, but for both security and 
> performance reasons, it will be entirely optional.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to