Uploaded image for project: 'Jackrabbit Oak'
  1. Jackrabbit Oak
  2. OAK-9321

Oak sessions should be refreshed before tail compaction

Agile BoardAttach filesAttach ScreenshotAdd voteVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 1.22.5
    • Fix Version/s: None
    • Component/s: jcr
    • Labels:
      None

      Description

      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.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              joerghoh Joerg Hoh

              Dates

              • Created:
                Updated:

                Issue deployment