[SERVER-27199] audit places where we call deleteRecord directly Created: 28/Nov/16  Updated: 23/Feb/17  Resolved: 16/Feb/17

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

Type: Bug Priority: Major - P3
Reporter: Geert Bosch Assignee: Maria van Keulen
Resolution: Done Votes: 0
Labels: neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-27930 Accessing cursor with pending data af... Closed
depends on SERVER-27996 Accessing system.namespaces cursor wi... Closed
depends on SERVER-28022 Accessing cursor with pending data af... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Storage 2017-03-06
Participants:

 Description   

There are places where we call deleteRecord directly for system collections, similar to the situation fixed in SERVER-24963. We need to audit and fix all these cases to properly perform invalidations.


Generated at Thu Feb 08 04:14:26 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.