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 "Jörg Hoh (Jira)" <ji...@apache.org> on 2021/01/13 11:10:00 UTC

[jira] [Created] (OAK-9321) Oak sessions should be refreshed before tail compaction

Jörg Hoh created OAK-9321:
-----------------------------

             Summary: Oak sessions should be refreshed before tail compaction
                 Key: OAK-9321
                 URL: https://issues.apache.org/jira/browse/OAK-9321
             Project: Jackrabbit Oak
          Issue Type: Improvement
          Components: jcr
    Affects Versions: 1.22.5
            Reporter: Jörg Hoh


Although discouraged since forever, long running JCR sessions are still seen quite often in applications I see.
One effect of these long running sessions is that in combination with tail compaction it can lead to SegmentNotFoundExceptions. These exceptions are not persistent, meaning that the storage layer is not affected. A restart will cause the SNFE to vanish until they appear again after some time.

Of course fixing the long running sessions is definitely the right way to fix this problem, but it'S unlikely that it can be fixed easily in all cases. Therefor I would propose to have a workaround, which refreshes all open sessions (older than 1h?) before performing tail compaction. It would be great, if the sessions would be logged, which are refreshed, so it can serve as input for the fixing.




--
This message was sent by Atlassian Jira
(v8.3.4#803005)