Details
-
Task
-
Resolution: Unresolved
-
Major - P3
-
None
-
None
-
None
-
Replication
-
Execution Team 2021-12-27, Execution Team 2022-01-10
Description
dbCheck logs batch results via a DeferredWriter, because it historically acquired a global S lock. As recent server versions allow acquiring more granular, less disruptive locks (SERVER-61748) we should be in a position to log synchronously. This will improve the user experience as the dbCheck command completion guarantees logging completion.
Attachments
Issue Links
- is related to
-
SERVER-61748 dbCheck should not hold a strong database lock during batches
-
- Closed
-