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/04/15 02:53:59 UTC

[jira] [Resolved] (ACCUMULO-3725) Majc trace tacked onto minc trace

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

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

> Majc trace tacked onto minc trace
> ---------------------------------
>
>                 Key: ACCUMULO-3725
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3725
>             Project: Accumulo
>          Issue Type: Bug
>          Components: trace
>            Reporter: Billie Rinaldi
>            Assignee: Billie Rinaldi
>             Fix For: 1.7.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> [~elserj] noticed an issue where a minorCompaction trace of length 10295 ms also contained spans for a major compaction starting at time offset 46336 ms.  Looking into this, it seems like MinorCompactionTask.run does the following:
> {noformat}
> start minc root span
> try {
>   minor compaction
>   maybe major compaction
> } finally {
>   stop minc root span
> }
> {noformat}
> The major compaction is async, so it gets initiated with the minor compaction span as its parent, then the minor compaction span is stopped, and at some point later the major compaction occurs.



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