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-2045) Long running JCR session prevent live cleanup in Segment FileStore
Date Tue, 04 Nov 2014 08:49:34 GMT

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

Michael Dürig commented on OAK-2045:

Much of the discussion also relating to this issue has currently moved to OAK-2192.

> Long running JCR session prevent live cleanup in Segment FileStore
> ------------------------------------------------------------------
>                 Key: OAK-2045
>                 URL: https://issues.apache.org/jira/browse/OAK-2045
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: segmentmk
>            Reporter: Chetan Mehrotra
>            Assignee: Chetan Mehrotra
>             Fix For: 1.2
>         Attachments: OAK-2045-segment-fault-approach-1.patch, OAK-2045-segment-fault-approach-2-path-based.patch,
OAK-2045-segment-fault-approach.patch, OAK-2045-test-fix.patch
> Cleanup operation in SegmentNodeStore detects the un referenced garbage and clean it
up. To determine the reference validity it starts with an initial set of SegmentId which have
a live java reference. 
> This works fine for simple setup but when Oak repository is used in an application (like
Sling) where application code can create long running session (for observation) then such
session are bound to old NodeState at time of startup. Such references prevent the cleanup
logic to remove older revisions while system is running. Such revisions can only be removed
via an offline compaction-> cleanup.
> Need to find out a way where we can _migrate_ such old NodeState references to newer

This message was sent by Atlassian JIRA

View raw message