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

Confusing log entries when memory requirements are not met at start of OnRC

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.7.7, 1.8.0
    • Component/s: segment-tar
    • Labels:

      Description

      When the memory requirements for running OnRC are not met before the estimation phase the estimator will run nevertheless. The process will only be cancelled at the beginning of the compaction phase. The entries in the log file reflect this:

      TarMK GC #1: canceling compaction because available memory level 306.4 MB (306395472 bytes) is too low...
      TarMK GC #1: estimation started
      TarMK GC #1: estimation completed in 343.5 ms (343 ms). Estimation skipped because of missing gc journal data (expected on first run)
      TarMK GC #1: running full compaction
      TarMK GC #1: compaction started ...
      TarMK GC #1: unable to estimate number of nodes for compaction, missing gc history.
      TarMK GC #1: compaction cancelled: Not enough memory.
      TarMK GC #1: cleaning up after failed compaction
      

      However they can easily be (mis-)read as compaction being re-triggered after having been cancelled and then being cancelled again.

        Attachments

          Activity

            People

            • Assignee:
              mduerig Michael Dürig
              Reporter:
              mduerig Michael Dürig
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: