Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Tue, 14 Oct 2014 14:21:34 +0000 (UTC)
From: "Josh Elser (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12623565.1355327299000.262993.1413296494808@Atlassian.JIRA>
In-Reply-To: <JIRA.12623565.1355327299000@Atlassian.JIRA>
References: <JIRA.12623565.1355327299000@Atlassian.JIRA>
 <JIRA.12623565.1355327299094@arcas>
Subject: [jira] [Commented] (ACCUMULO-898) look into replacing cloudtrace
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/ACCUMULO-898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14170988#comment-14170988 ] 

Josh Elser commented on ACCUMULO-898:
-------------------------------------

IMO, we should try to keep as much compatibility with existing accumulo-trace as we can for the first go around, and then we can think about if it would make sense to get rid of accumulo-trace after the fact. I don't think we have to try to do both in the first pass.

> look into replacing cloudtrace
> ------------------------------
>
>                 Key: ACCUMULO-898
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-898
>             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, trace-zipkin.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
(v6.3.4#6332)