[
https://issues.apache.org/jira/browse/OAK-4657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrei Dulceanu updated OAK-4657:
---------------------------------
Attachment: OAK-4657-01.patch
Exposed {{reclaimedSize}} from {{FileStore.cleanup()}} through
{{FileStoreStatsMBean.getReclaimedSizeStatsAsCount()}} and
{{FileStoreStatsMBean.getReclaimedSizeStatsAsCompositeData()}}. Created a new
test in {{CompactionAndCleanupIT.concurrentWritesDuringCleanup()}} to prove
that the changes done in OAK-4106 actually work.
This patch needs to be applied after the one from OAK-4106, because the
previous implementation for {{reclaimedSize}} reports negative numbers, thus
breaking the new test.
[~mduerig][~chetanm] Could you take a look at this patch?
> Add metric for FileStore cleanup reclaimed size
> -----------------------------------------------
>
> Key: OAK-4657
> URL: https://issues.apache.org/jira/browse/OAK-4657
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: segment-tar
> Affects Versions: Segment Tar 0.0.10
> Reporter: Andrei Dulceanu
> Assignee: Andrei Dulceanu
> Priority: Minor
> Attachments: OAK-4657-01.patch
>
>
> It would be good to have a metric to capture the number of bytes actually
> removed from disk after each cleanup cycle. Looking at repository size
> before/after cleanup can be misleading as concurrent writes can happen in
> between.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
