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 2017/11/06 16:40:00 UTC

[jira] [Commented] (OAK-6886) OffRC always logs 0 for the number of compacted nodes in gc.log

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

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

Making OAK-6909 and OAK-6910 blockers for this issue as the initial patch is IMO still the right approach but would need these issues fixed as a prerequisite.

> OffRC always logs 0 for the number of compacted nodes in gc.log
> ---------------------------------------------------------------
>
>                 Key: OAK-6886
>                 URL: https://issues.apache.org/jira/browse/OAK-6886
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: segment-tar
>            Reporter: Michael Dürig
>            Assignee: Michael Dürig
>              Labels: compaction, gc
>             Fix For: 1.8, 1.7.12
>
>
> After an offline compaction the {{gc.log}} always contains 0 for the number of compacted nodes. This is caused by {{org.apache.jackrabbit.oak.segment.tool.Compact.compact()}} instantiating a new {{FileStore}} to run cleanup. That file store has new {{GCMonitor}} instance, which did no see any of the nodes written by the compaction that was run on the previous {{FileStore}} instance. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)