[
https://issues.apache.org/jira/browse/OAK-6033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15958815#comment-15958815
]
Francesco Mari commented on OAK-6033:
-------------------------------------
Further investigations showed that the issue is not caused by a particular
interleaving of the commit and cleanup operations, but from an incomplete
accounting of the references to segments in memory. The situation is created by
a data segment that is not yet persisted but references bulk segments that are
already persisted. The data segment, even if not yet persisted, should
contribute its pending references to the input of the cleanup operation.
> Test failure: CompactionAndCleanupIT.concurrentCleanup
> ------------------------------------------------------
>
> Key: OAK-6033
> URL: https://issues.apache.org/jira/browse/OAK-6033
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: segment-tar
> Reporter: Michael Dürig
> Assignee: Francesco Mari
> Labels: gc, test-failure
> Fix For: 1.7.0, 1.8
>
>
> That test fails for me on every 2nd run or so. This seems to be a regression
> introduced with OAK-6002.
> {code}
> org.junit.ComparisonFailure: Expected nothing to be cleaned but generation
> 'b' for file data00002b.tar indicates otherwise.
> Expected :a
> Actual :b
> at org.junit.Assert.assertEquals(Assert.java:115)
> org.apache.jackrabbit.oak.segment.CompactionAndCleanupIT.concurrentCleanup(CompactionAndCleanupIT.java:1252)
> {code}
> [~frm], could you have a look?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
