[SERVER-48578] Skip fast count enforcement on the oplog when running validate with enforceFastCount=true Created: 03/Jun/20  Updated: 29/Oct/23  Resolved: 30/Jun/20

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 4.7.0

Type: Bug Priority: Major - P3
Reporter: Gregory Noma Assignee: Gregory Noma
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Documented
is documented by DOCS-13740 Investigate changes in SERVER-48578: ... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Execution Team 2020-06-29, Execution Team 2020-07-13
Participants:
Linked BF Score: 34

 Description   

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.



 Comments   
Comment by Githook User [ 30/Jun/20 ]

Author:

{'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}

Message: SERVER-48578 Skip fast count enforcement on the oplog when running validate with enforceFastCount=true
Branch: master
https://github.com/mongodb/mongo/commit/0e8d62d77db2e6b7682e13345d68959fd1c122ce

Generated at Thu Feb 08 05:17:31 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.