Details
-
Task
-
Status: Closed
-
Major - P3
-
Resolution: Gone away
-
None
-
None
-
true
Description
Description
SERVER-44650 added the enforceFastCount mode to the validate command (documented by DOCS-13667). This ticket makes it so that the fast count will not be enforced when validate is run on the oplog collection, even if enforceFastCount is set to true (in other words, the enforceFastCount flag is ignored when validate is run on local.oplog.rs).
Description of Linked Ticket
Oplog writers only take a global IX lock, so the oplog can still be written to even during full validation despite its collection X lock. This can cause validate to incorrectly report an incorrect fast count on the oplog when run in enforceFastCount mode. Thus, even if enforceFastCount is specified, the fast count should not be enforced on the oplog.
Scope of changes
Impact to Other Docs
MVP (Work and Date)
Resources (Scope or Design Docs, Invision, etc.)
Attachments
Issue Links
- documents
-
SERVER-48578 Skip fast count enforcement on the oplog when running validate with enforceFastCount=true
-
- Closed
-
- related to
-
DOCS-13667 Investigate changes in SERVER-44650: New test mode for foreground validate that doesn't silently fix fastcounts
-
- Closed
-