Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-12033

Improve (background) compact related stats

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Compaction
    • 3
    • StorEng - Defined Pipeline

      Find below an example of stats generated by background compaction:

          "background-compact": {
            "background compact failed calls": 0,
            "background compact failed calls due to cache pressure": 0,
            "background compact interrupted": 0,
            "background compact moving average of bytes rewritten": 0,
            "background compact recovered bytes": 0,
            "background compact running": 1,
            "background compact skipped file as it is part of the exclude list": 0,
            "background compact skipped file as not meeting requirements for compaction": 140,
            "background compact successful calls": 14,
            "background compact timeout": 0,
            "number of files tracked by background compaction": 14
          },
      

      Something that is misleading is the background compact successful calls. This stats is incremented every time the compact method has been called successfully but it does not mean compaction has done anything - it simply means the code was executed gracefully. This can lead to misinterpretation and could be revisited.

            Assignee:
            backlog-server-storage-engines [DO NOT USE] Backlog - Storage Engines Team
            Reporter:
            etienne.petrel@mongodb.com Etienne Petrel
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: