[
https://issues.apache.org/jira/browse/HBASE-6449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13423508#comment-13423508
]
stack commented on HBASE-6449:
------------------------------
bq. I meant having htrace as an independent maven project in the hbase source
tree and add a <dependency> for htrace in hbase's pom.
But sounds like your intent is a generic tracing library going by statements
above? Is that so? If that is the case, it seems odd dev'ing a generic lib
inside in HBase core. You should do it as its own project I'd say; you can
move faster and it'll be easier keep your generic focus. HBase project, IMO,
will gladly be your guinea pig/proofing ground for your tracing lib work since
we need tracing so bad. We can review/exercise your lib, we can add it as a
dependency and make the necessary changes to pull it in and make it easy
starting/stopping a trace, etc. but unless you think otherwise, lets keep the
coupling loose.
Correct me if I'm off Jonathan.
> 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
