-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Execution
-
Fully Compatible
-
ALL
-
v8.2, v8.0, v7.0
-
Execution Team 2024-11-11, Execution Team 2024-12-23, Execution Team 2025-01-06, Execution Team 2025-01-20, Storage Execution 2025-08-04
-
200
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
-
None
In rare circumstances, it is possible for BatchedDeleteStage to enqueue the same document twice for deletion and then attempt two deletes of that document, with the second attempt triggering an unnecessary warning.
When refactoring BatchedDeleteStage for this project, we should add logic to prevent already enqueued documents from getting added to the queue a second time.
- related to
-
SERVER-108578 Investigate if Replication / RSS can strengthen its boundaries to allow only sane oplog entries
-
- Backlog
-
-
SERVER-90997 Relax the assertion when the document is not found in doDeleteRecord()
-
- Closed
-