Uploaded image for project: 'Jackrabbit Oak'
  1. Jackrabbit Oak
  2. OAK-3001 Simplify JournalGarbageCollector using a dedicated timestamp property
  3. OAK-5119

JournalGarbageCollector: journalGcBatchSize configuration is irrelevant post implementation tasks of bulk remove support in DocumentStore

Attach filesAttach ScreenshotVotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Technical task
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.5.14, 1.6.0
    • Component/s: documentmk
    • Labels:
      None

      Description

      Following up with this comment:

      ... noticed OAK-3975 in related issues. I think we should revert that configuration and code for house-keeping/maintenance!?

      OAK-3875 added a configuration to DocumentNodeStoreService to have configurable batch sizes while removing journal entries. With implementation tasks of OAK-3001, we do bulk remove at persistence layer and hence batched query isn't required. Thus, the configuration should be removed.

        Attachments

          Activity
          $i18n.getText('security.level.explanation', $currentSelection) Viewable by All Users
          Cancel

            People

            • Assignee:
              catholicon Vikas Saurabh
              Reporter:
              catholicon Vikas Saurabh

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment