[SERVER-51198] Investigate whether the oplog collection can ever be modified Created: 28/Sep/20  Updated: 16/Nov/20  Resolved: 13/Nov/20

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

Type: Task Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Henrik Edin
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-52878 Separate oplog from regular collections Closed
Sprint: Execution Team 2020-12-14
Participants:

 Description   

Collection copy-on-write functionality is disabled for the Oplog collection because LocalOplogInfo holds onto a oplog collection pointer that would become unsafe. However, if such copy-on-write operations are not allowed against the oplog collection, then we wouldn't need to keep logic around to modify the existing Collection instances, in addition to the new Collection copy-on-write logic.


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