[jira] [Commented] (OAK-3527) Improve logging for blob GC

["Amit Jain (JIRA)" <ji...@apache.org>]

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

Amit Jain commented on OAK-3527:
--------------------------------

[~mduerig]
We already have logging at INFO level. See

{noquote}
13:27:12.039 INFO  [main] MarkSweepGarbageCollector.java:242 Starting Blob garbage collection
13:27:12.107 INFO  [main] MarkSweepGarbageCollector.java:524 Number of valid blob references marked under mark phase of Blob garbage collection [6]
13:27:12.168 INFO  [main] MarkSweepGarbageCollector.java:625 Number of blobs present in BlobStore : [10] 
13:27:12.215 INFO  [main] MarkSweepGarbageCollector.java:250 Blob garbage collection completed in 175.4 ms. Number of blobs deleted [4]
{noquote}

> Improve logging for blob GC
> ---------------------------
>
>                 Key: OAK-3527
>                 URL: https://issues.apache.org/jira/browse/OAK-3527
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: blob
>            Reporter: Michael Dürig
>            Assignee: Amit Jain
>             Fix For: 1.4
>
>
> We should have better insight on the gc progress on big data stores:
> * Once it has done its scan, we should have a log line at INFO level on how big a list of stuff it built to them work on removing.  
> * Subsequently, and more importantly, we need a log line at INFO level that says when it has finished removing everything on the list it built.  
> This is especially important regarding synchronization with Cold Standby, in that once it has finished it's removing phase, one would then want to rsync the filedatastore.



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