jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Francesco Mari (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-4165) Too verbose logging during revision gc
Date Tue, 03 May 2016 13:44:13 GMT

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

Francesco Mari commented on OAK-4165:

I decided to apply the patch directly to the 1.4 branch because of the [~mduerig]'s comment.
It seems that forward references are not computed anymore because of OAK-3348.

> Too verbose logging during revision gc
> --------------------------------------
>                 Key: OAK-4165
>                 URL: https://issues.apache.org/jira/browse/OAK-4165
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: segment-next
>            Reporter: Michael Dürig
>            Assignee: Francesco Mari
>            Priority: Blocker
>              Labels: cleanup, gc, logging
>             Fix For: 1.4, 1.4.2
>         Attachments: OAK_4165.patch
> {{FileStore.cleanup}} logs the segment id of any forward reference found when including
those in the reference graph. The logged information can amount to several MBs impacting normal
operation. Furthermore the actually reclaimed segments are logged, which also makes the log
files explode. Finally the processing of the references and individual tar files might be
too wordy. 

This message was sent by Atlassian JIRA

View raw message