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/11 14:04:20 UTC

[jira] [Updated] (OAK-4667) Create IT to validate that reclaimed size after cleanup is always positive

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

Andrei Dulceanu updated OAK-4667:
---------------------------------
    Description: As OAK-4106 reworked the way {{reclaimedSize}} is computed, it would be nice to have an IT to validate the assumption that under the new circumstances this value is always positive. Of particular interest here is the scenario in which concurrent writes interweave with the cleanup process.  (was: As OAK-4601 reworked the way {{reclaimedSize}} is computed, it would be nice to have an IT to validate the assumption that under the new circumstances this value is always positive. Of particular interest here is the scenario in which concurrent writes interweave with the cleanup process.)

> Create IT to validate that reclaimed size after cleanup is always positive
> --------------------------------------------------------------------------
>
>                 Key: OAK-4667
>                 URL: https://issues.apache.org/jira/browse/OAK-4667
>             Project: Jackrabbit Oak
>          Issue Type: Test
>          Components: segment-tar
>    Affects Versions: Segment Tar 0.0.10
>            Reporter: Andrei Dulceanu
>            Assignee: Andrei Dulceanu
>            Priority: Minor
>
> As OAK-4106 reworked the way {{reclaimedSize}} is computed, it would be nice to have an IT to validate the assumption that under the new circumstances this value is always positive. Of particular interest here is the scenario in which concurrent writes interweave with the cleanup process.



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