[SERVER-63863] Write conflict exception handling for batched multi-deletes Created: 21/Feb/22  Updated: 29/Oct/23  Resolved: 22/Mar/22

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

Type: Task Priority: Major - P3
Reporter: Josef Ahmad Assignee: Haley Connelly
Resolution: Fixed Votes: 0
Labels: PM-2227-M1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2022-03-07, Execution Team 2022-03-21, Execution Team 2022-04-04
Participants:
Linked BF Score: 66

 Description   

Handle and validate transparent retryability on write conflict exception, similar to what the doc-by-doc DeleteStage does.



 Comments   
Comment by Githook User [ 22/Mar/22 ]

Author:

{'name': 'Haley Connelly', 'email': 'haley.connelly@mongodb.com', 'username': 'haleyConnelly'}

Message: SERVER-63863 Disable BatchedDeleteStagedDocIsDeletedWriteConflict running in EphemeralForTest
Branch: master
https://github.com/mongodb/mongo/commit/330c702d55b4a2cfb98dd86630c7e7820e5657c1

Comment by Githook User [ 21/Mar/22 ]

Author:

{'name': 'Haley Connelly', 'email': 'haley.connelly@mongodb.com', 'username': 'haleyConnelly'}

Message: SERVER-63863 Handle Write Conflicts in BATCHED_DELETE stage
Branch: master
https://github.com/mongodb/mongo/commit/f545643dd257f1c2bd14e0fcead994fc27ac5dba

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