Description
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:
start minc root span
try {
minor compaction
maybe major compaction
} finally {
stop minc root span
}
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.
Attachments
Issue Links
- is related to
-
ACCUMULO-3802 Backport majc in minc trace to 1.6
-
- Resolved
-
There are no Sub-Tasks for this issue.
