jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Dürig (JIRA) <j...@apache.org>
Subject [jira] [Commented] (OAK-2795) TarMK revision cleanup message too verbose.
Date Wed, 15 Jul 2015 15:56:04 GMT

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

Michael Dürig commented on OAK-2795:

Unscheduling as for now we need those message. The suggestion is to configure logging such
that those messages are not logged, which will adversely impact post mortem analysis in the
case of an SNFE. 

> TarMK revision cleanup message too verbose.
> -------------------------------------------
>                 Key: OAK-2795
>                 URL: https://issues.apache.org/jira/browse/OAK-2795
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: segmentmk
>            Reporter: Zygmunt Wiercioch
>            Priority: Minor
>              Labels: gc
> The segment GC message can be thousands of lines long on a system which experienced a
lot of activity.  For example, in my test, I had:
> {noformat}
> org.apache.jackrabbit.oak.plugins.segment.file.TarReader-GC Cleaned segments from data00008a.tar:

>  4b6882e7-babe-4854-a966-c3a630c338c6, 506a2eb3-92a6-4b83-a320-5cc5ac304302, f179e4b1-acec-4a5d-a686-bf5e97828563,
> {noformat}
> followed by approximately 40,000 more lines.

This message was sent by Atlassian JIRA

View raw message