[
https://issues.apache.org/jira/browse/HBASE-6449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13423482#comment-13423482
]
Jonathan Leavitt commented on HBASE-6449:
-----------------------------------------
bq. What do you mean by having hbase dependent on htrace?
I meant having htrace as an independent maven project in the hbase source tree
and add a <dependency> for htrace in hbase's pom.
The original plan was to get the tracing library committed to hbase first so
the hbase committers could review and would be more likely to commit the
necessary hooks into hbase. It would also save the initial hassle of getting
the library into maven.
But you would recommend putting it on github, and only submitting patches with
the instrumentation for hbase? If htrace were on github and the hooks were in
hbase, would those downloading hbase source just have to grab htrace off github
and have maven install it locally?
> Dapper like tracing
> -------------------
>
> Key: HBASE-6449
> URL: https://issues.apache.org/jira/browse/HBASE-6449
> Project: HBase
> Issue Type: New Feature
> Components: client, ipc
> Affects Versions: 0.96.0
> Reporter: Jonathan Leavitt
> Labels: tracing
> Attachments: htrace1.diff, trace.png
>
>
> 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
