[
https://issues.apache.org/jira/browse/OAK-5983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16201539#comment-16201539
]
Amit Jain commented on OAK-5983:
--------------------------------
Added estimate of the size calculated for cases having length encoded in the id
with http://svn.apache.org/viewvc?rev=1811914&view=rev
This leaves out the estimate for Mongo/RDBBlobStore blobs and no length encoded
blob ids (for example from upgraded systems). This should cover most use cases
though.
I am hesitant to add code at this point to cover cases with no length encoding
which would require a remote call because deletion phase is already the slowest
part and would add significant time for large datastores.
> BlobGC should log the amount of space reclaimed after GC run is done
> --------------------------------------------------------------------
>
> Key: OAK-5983
> URL: https://issues.apache.org/jira/browse/OAK-5983
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: blob
> Reporter: Chetan Mehrotra
> Assignee: Amit Jain
> Fix For: 1.8, 1.7.10
>
>
> Currently BlobGC logic reports the number of blobs removed
> {noformat}
> 24.03.2017 12:33:33.120 *INFO* [sling-oak-observation-205]
> org.apache.jackrabbit.oak.plugins.blob.MarkSweepGarbageCollector Blob garbage
> collection completed in 16.76 s. Number of blobs deleted [1776] with max
> modification time of [2017-03-23 12:33:16.373]
> {noformat}
> It would helpful it can also report the size reclaimed by deleted those blobs
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
