[
https://issues.apache.org/jira/browse/KUDU-1956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15941261#comment-15941261
]
Todd Lipcon commented on KUDU-1956:
-----------------------------------
Sure enough just before the crash another compaction finished on a different
thread which had compacted away the two above-referenced rowsets.
> Crash with "rowset selected for compaction but not available anymore"
> ---------------------------------------------------------------------
>
> Key: KUDU-1956
> URL: https://issues.apache.org/jira/browse/KUDU-1956
> Project: Kudu
> Issue Type: Bug
> Components: tablet
> Affects Versions: 1.3.0
> Reporter: Todd Lipcon
> Priority: Critical
>
> I loaded 1T of data into a server with 8 MM threads configured, and a patch
> to make the MM thread wake up and do scheduling as soon as any prior op
> finished. After a day or two of runtime the TS crashed with:
> E0324 14:28:19.733708 5801 tablet.cc:1207] T
> cf12905ff7d84fa0b4148aab292f0c40 P 40b48ecb131449c58df26f62ccc35538: Rowset
> selected for compaction but not available anymore: RowSet(22755)
> E0324 14:28:19.733762 5801 tablet.cc:1207] T
> cf12905ff7d84fa0b4148aab292f0c40 P 40b48ecb131449c58df26f62ccc35538: Rowset
> selected for compaction but not available anymore: RowSet(24031)
> F0324 14:28:19.733777 5801 tablet.cc:1210] T
> cf12905ff7d84fa0b4148aab292f0c40 P 40b48ecb131449c58df26f62ccc35538: Was
> unable to find all rowsets selected for compaction
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
