You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Andrei Dulceanu (JIRA)" <ji...@apache.org> on 2016/08/25 07:33:20 UTC

[jira] [Commented] (OAK-4699) Random failure in CompactionAndCleanupIT#concurrentWritesCleanupNoNewGen

    [ https://issues.apache.org/jira/browse/OAK-4699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15436416#comment-15436416 ] 

Andrei Dulceanu commented on OAK-4699:
--------------------------------------

Yes, I think you are right. That test was derived from {{#concurrentWritesCleanupZeroReclaimedSize}} and that's why it ended up doing things concurrently. I looked over the patch and the changes are ok.

> Random failure in CompactionAndCleanupIT#concurrentWritesCleanupNoNewGen
> ------------------------------------------------------------------------
>
>                 Key: OAK-4699
>                 URL: https://issues.apache.org/jira/browse/OAK-4699
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: segment-tar
>            Reporter: Francesco Mari
>             Fix For: Segment Tar 0.0.12
>
>         Attachments: OAK-4699-01.patch
>
>
> The test {{CompactionAndCleanupIT#concurrentWritesCleanupNoNewGen}} fails randomly on my machine. 
> The failure of this test seems to be caused by the cleanup running concurrently with the write tasks. The test seems to assert that no new generations of TAR files are created if there is no need for it. If this is the case, there is no need to execute the workers and the cleanup concurrently.



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