hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-6449) Dapper like tracing
Date Thu, 26 Jul 2012 20:55:34 GMT

    [ https://issues.apache.org/jira/browse/HBASE-6449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13423458#comment-13423458

stack commented on HBASE-6449:

bq. Do you think it is best to add it as a module as opposed to keeping it completely independent,
and just having hbase depend on it?

I think it best to have it as an independent project, at least at first (you don't need our
blessing to do such a thing).  Make a patch for hbase core that gives you the hooks you need
and we'll commit that but better if all the rest can live outside especially as its being
developed (no lag waiting on a committer to review and commit; just do it yourself out in
github or wherever).

What do you mean by having hbase dependent on htrace?
> 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


View raw message