[SERVER-82864] Handle WriteConflict errors in fle2_contention_kill_parent.js Created: 07/Nov/23  Updated: 07/Nov/23  Resolved: 07/Nov/23

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

Type: Task 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

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Sprint: Security 2023-11-13
Participants:
Linked BF Score: 45

 Description   

In v6.0, the fle2_contention_kill_parent.js can encounter WriteConflict errors when performing an encrypted update that follows a previous killed encrypted update operation (provided that the same contention factor value is coincidentally selected).

This is because per SERVER-70247, if an ongoing internal transaction gets cancelled by a killOp, the transaction just lingers in an idle state until later reaped by another background job. If the killed transaction has managed to write to the ESC collection, then the following transaction can potentially write the same _id value if the same contention factor is used, which causes a write conflict on the _id index.


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