-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Internal Code, Storage
-
None
-
Storage Engines - Server Integration
-
Fully Compatible
-
None
-
None
-
None
-
None
-
None
-
None
-
None
That code dates from a time when we thought that concurrent writes to non-oplog capped collections made sense. Now that we've realized that it doesn't we can significantly simplify the code. All handling of out-of-order commits should only be for the oplog case and not for normal capped collections.