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 "Michael Dürig (JIRA)" <ji...@apache.org> on 2015/12/16 16:05:46 UTC

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

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

Michael Dürig commented on OAK-3527:
------------------------------------

[~amitjain], could you look into this?

> 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)