You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Billie Rinaldi (JIRA)" <ji...@apache.org> on 2015/06/01 15:32:17 UTC

[jira] [Resolved] (ACCUMULO-3862) Improve how AsyncSpanReceiver drops short spans

     [ https://issues.apache.org/jira/browse/ACCUMULO-3862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Billie Rinaldi resolved ACCUMULO-3862.
--------------------------------------
    Resolution: Fixed

> Improve how AsyncSpanReceiver drops short spans
> -----------------------------------------------
>
>                 Key: ACCUMULO-3862
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3862
>             Project: Accumulo
>          Issue Type: Bug
>          Components: trace
>    Affects Versions: 1.5.0, 1.5.1, 1.5.2, 1.6.0, 1.6.1, 1.6.2, 1.7.0
>            Reporter: Billie Rinaldi
>            Assignee: Billie Rinaldi
>             Fix For: 1.7.1, 1.8.0
>
>         Attachments: ACCUMULO-3862.1.patch, ACCUMULO-3862.2.patch, ACCUMULO-3862.3.patch
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> It just occurred to me that we are dropping 0ms spans when we poll the sendQueue for a span to deliver via thrift.  It would cause less churn in the queue if we dropped the span as soon as we received it, before inserting it into the queue.
> This is already fixed in 1.6.3 which no longer drops 0ms spans.  It is only really a concern in 1.7.0 if you are using HDFS tracing, which generates a LOT of 0ms spans.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)