[SERVER-77238] QE anchor cleanup should fail when it encounters write errors Created: 17/May/23  Updated: 29/Oct/23  Resolved: 22/May/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.1.0-rc0

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

Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Security 2023-05-29
Participants:

 Description   

Currently, the cleanupESCAnchors function, which is used by cleanupStructuredEncryptionData command, only logs a warning when it runs into write errors while performing the anchor deletes. This is an issue because if the anchors are not being deleted due to these ignored errors, and the cleanup command then drops the "esc.deletes" collection, then these anchors will never be removed from the ESC because subsequent cleanup calls will only record anchor IDs starting from the new "bottom" position in the null anchor.

Therefore, if a write error occurs during the anchor removal, it should stop the entire cleanup operation so that the "esc.deletes" collection won't be dropped.  Subsequent calls to cleanup can then resume deletions from the leftover "esc.deletes" collection.

 



 Comments   
Comment by Githook User [ 20/May/23 ]

Author:

{'name': 'Erwin Pe', 'email': 'erwin.pe@mongodb.com', 'username': 'erwee'}

Message: SERVER-77238 QE anchor cleanup should fail on write errors
Branch: master
https://github.com/mongodb/mongo/commit/1e464181c00979977ee67fb7a05274b007c594d0

Generated at Thu Feb 08 06:34:55 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.