Add metrics/logging to increase visibility into the oplog sampling process

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.2.1, 8.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Engines, Storage Engines - Server Integration
    • Fully Compatible
    • SESI - 2025-06-24, SESI - 2025-07-08, Addy BBBQ'd Greg - 2025-07-22, Epicurean - 2025-08-05, TheReturnOfAaron - 2025-08-19, WhatThePelly - 2025-09-02
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      This ticket also includes the investigation of relevant metrics/logging that can be introduced to increase visibility into the oplog sampling process and identifying any new ones to be added once we have made sampling async. Some ideas include:

      • The progress with the number of truncation markers created during sampling.
      • The state of the sampling thread at regular intervals (e.g., active, idle).
      • The oplog growth rate throughout the sampling period.
      • How much time has elapsed between startup finishing and sampling finishing.

      This ticket can be further subdivided into other tickets as needed.

            Assignee:
            Adeline Chen
            Reporter:
            Clarisse Cheah
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: