- 
    Type:Bug 
- 
    Resolution: Fixed
- 
    Priority:Major - P3 
- 
    Affects Version/s: 6.0.11
- 
    Component/s: None
- 
        Storage Execution
- 
        Fully Compatible
- 
        ALL
- 
        v8.1, v8.0, v7.0, v6.0
- 
        Storage Execution 2025-06-09, Storage Execution 2025-06-23
- 
        200
- 
        None
- 
        None
- 
        None
- 
        None
- 
        None
- 
        None
- 
        None
Oplog slots can be reserved for inserts prior to taking an exclusive lock on the metadata resource.
This can generate the following ordering on the primary
| Insert 1 | Insert 2 | 
|---|---|
| Reserve oplog slot with TS(1) | |
| Reserve oplog slot with TS(2) | |
| X-lock resource | |
| Insert document with RID(1) | |
| X-lock resource | |
| Insert document with RID(2) | 
On the secondary, we apply oplog entries serially for non-clustered capped collections. So we would apply oplog entry TS(1) with RID(1) and oplog entry TS(2) with RID(2) as record IDs are not globally unique. This results in a different natural order between the primary and secondaries, which we guarantee for capped collections.
The same might be possible for updates and deletes.
- is depended on by
- 
                    SERVER-86692 dbhash doesn't check natural order for capped collections with _id index -         
- Closed
 
-         
- is duplicated by
- 
                    SERVER-87852 capped collection write workload can negatively impact other workload in the system -         
- Closed
 
-         
- is related to
- 
                    SERVER-106534 Add IngressRequestRateLimiter parameters to config fuzzer -         
- Open
 
-         
- related to
- 
                    SERVER-82752 Writers can skip acquiring resource metadata lock for capped collection in 4.4 and older versions. -         
- Closed
 
-         
- 
                    SERVER-106354 Missing resource lock acquisition when applying batch of inserts to a capped collection -         
- Closed
 
-         
- 
                    SERVER-82863 Add support for the new capped collection option 'allowConcurrentWrites'. -         
- Closed
 
-         
- 
                    SERVER-87852 capped collection write workload can negatively impact other workload in the system -         
- Closed
 
-         
- 
                    SERVER-106005 Always scan capped collections in natural order for dbhash -         
- Blocked
 
-