[
https://issues.apache.org/jira/browse/HBASE-6449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13421650#comment-13421650
]
Jonathan Leavitt commented on HBASE-6449:
-----------------------------------------
[Dapper | http://research.google.com/pubs/pub36356.html] is google's system to
trace requests through their systems.
The paper discusses how useful Google engineers find the system, as well as
laying out the basic design of the system.
Accumulo added tracing to their project based on the Dapper design. They call
it cloudtrace. I have used Accumulo's cloudtrace as a starting point for a
tracing library. I modified it to not be dependent on any particular RPC
framework, as well as adding more detailed sampling, among other changes. I
plan to commit this to the hbase source tree as an independent maven project. I
will then submit commits that properly instrument HBase to use the tracing
library. This requires adding an optional payload to the protobuf RPC's
containing two 64bit id's: one for the trace id and another for the unique id
of the span that sent the message. There will be no additional data in the
messages when tracing is not active. The tracing library works by storing
information in ThreadLocal's. In order to preserve this information across
thread changes, the thread changes must be tracked. The tracing package
accomplishes this by wrapping any thread changes to pass the information
through to the new thread. I have done most of the instrumentation for HBase.
> Dapper like tracing
> -------------------
>
> Key: HBASE-6449
> URL: https://issues.apache.org/jira/browse/HBASE-6449
> Project: HBase
> Issue Type: New Feature
> Components: client, ipc
> Reporter: Jonathan Leavitt
> Labels: tracing
>
> Add [Dapper|http://research.google.com/pubs/pub36356.html] like tracing to
> HBase. [Accumulo|http://accumulo.apache.org] added something similar with
> their cloudtrace package.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
