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

revisionGC leaves garbage around, for often-changed nodes

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

Details

    • Bug
    • Status: Closed
    • Critical
    • Resolution: Fixed
    • 1.0.8
    • 1.0.10
    • core
    • None
    • 1.0.8.r1644758

    Description

      With oak-core 1.0.8.r1644758 we're seeing revision garbage piling up - even though revisionGC runs regularly (every night) and does not complain about any failures.

      This happens with often-changed nodes, ie with nodes that get more changes that fit into a mongo document, thus get split between revisionGC-runs.

      As a negative side-effect of this, the observation event generating (ie diffImpl) seems to have problems with such revision garbage and performs tremendously slow - presumably because all garbage-revisions are read even though the diff should be very small (ie the fromRev/toRev are only a few seconds, if ever minutes apart) - but I'll file a separate ticket about this.

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            chetanm Chetan Mehrotra
            stefanegli Stefan Egli
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment