accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Billie Rinaldi (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-898) look into replacing cloudtrace
Date Tue, 14 Oct 2014 14:00:53 GMT


Billie Rinaldi commented on ACCUMULO-898:

[~ctubbsii], [~ecn] could we discuss this comment:

bq. Ideally, the patch should remove the accumulo-trace module entirely, in favor of the dependency
on the htrace library; only the accumulo-tracer module should be left.

This doesn't seem compatible with Eric's suggestion on reviewboard that we attempt to preserve
current usage and make as few code changes as possible.  We could proceed with the plan of
moving everything to core or tracer, while leaving the user-facing classes from the trace
module deprecated instead of deleting them.  My main question is about the thrift TInfo object,
which is currently in the trace module and is used by all of the thrift Service classes. 
Moving this to core will change a significant amount of (generated) code, so I'd like to make
sure we want to do that.

> look into replacing cloudtrace
> ------------------------------
>                 Key: ACCUMULO-898
>                 URL:
>             Project: Accumulo
>          Issue Type: Improvement
>            Reporter: Eric Newton
>            Assignee: James Fiori
>             Fix For: 1.7.0
>         Attachments: ACCUMULO-898-1.patch, Cloudtrace Replacement Design Doc.pdf, trace-tracer.png,
> HBase has created their own distributed tracing library, and today I bumped into zipkin.
 zipkin has a reasonable visualization, and seems to work with thrift.  We should look into
replacing our tracing with one of these.

This message was sent by Atlassian JIRA

View raw message