-
Type:
Task
-
Resolution: Duplicate
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Engines, Storage Engines - Server Integration
-
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
-
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.
- depends on
-
SERVER-94681 Move sampling to the oplog cap maintainer thread
-
- Closed
-
-
SERVER-106314 Handle parallel marker creation
-
- Closed
-
- is related to
-
SERVER-94681 Move sampling to the oplog cap maintainer thread
-
- Closed
-