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 "Alex Parvulescu (JIRA)" <ji...@apache.org> on 2016/05/03 15:23:13 UTC

[jira] [Commented] (OAK-4165) Too verbose logging during revision gc

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

Alex Parvulescu commented on OAK-4165:
--------------------------------------

bq. Patch committed in r1742068.
I think this should have been applied to trunk and then merged. We still have the {{oak-segment}} present on trunk, even if in maintenance mode only.

> 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
(v6.3.4#6332)