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 Thu, 09 Oct 2014 21:47:34 GMT


Billie Rinaldi commented on ACCUMULO-898:

bq. The patch wouldn't apply cleanly with git am
Is that due to whitespace errors?  Those errors are in the generated thrift classes.  Do we
reformat those?

bq. Since the SpanReceivers and related utilities are associated with the accumulo-tracer
service, they should probably be moved there.
I was worried about the dependency hierarchy there, since the jar containing the SRs will
have to be added to the Hadoop classpath, and we probably don't want to be adding a bunch
of jars.  Though of course we don't really want there to be entire Accumulo modules with just
a couple of classes in them either.  Maybe it would be okay if dependencies on core and other
modules don't creep into the SRs.

bq. I'm not sure I understand the distinction in roles the SpanReceiverHost is supposed to
serve, vs. the TraceUtil.
SpanReceiverHost is kind of copied from Hadoop, from when we were planning to share the config,
with the idea of switching over to using Hadoop's version at some point.  But if we're not
sharing config, there's no need to preserve it.

> 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