Move sampling to the oplog cap maintainer thread

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
    • CookieFloss - 29/10/24, Party@Gregs - 2024-11-12, TeamTummy - 2024-11-26, SESI - 2025-06-24, SESI - 2025-07-08, Addy BBBQ'd Greg - 2025-07-22, Epicurean - 2025-08-05, TheReturnOfAaron - 2025-08-19
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently progressing on startup recovery is blocked on oplog sampling completing. There can be long running oplog sampling processes depending on the size of the oplog and how cold the datafiles are at startup. This can result in adding non-trivial amounts of time to restore.

      This ticket should aim to make oplog sampling asynchronous and do it in the background so that startup recovery can proceed and we will begin truncating the oplog whenever sampling is done.

      This ticket will add the sampling mechanism to the currently asynchronous oplog cap maintainer thread.

            Assignee:
            Clarisse Cheah
            Reporter:
            Clarisse Cheah
            Votes:
            0 Vote for this issue
            Watchers:
            14 Start watching this issue

              Created:
              Updated:
              Resolved: