[SERVER-71379] Ensure error propagation from internal transaction for all single write without shard key commands Created: 15/Nov/22  Updated: 29/Oct/23  Resolved: 09/Jan/23

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

Type: Task Priority: Major - P3
Reporter: Sanika Phanse (Inactive) Assignee: Sanika Phanse (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Assigned Teams:
Sharding NYC
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2022-12-12, Sharding NYC 2022-12-26, Sharding NYC 2023-01-09, Sharding NYC 2023-01-23
Participants:
Linked BF Score: 129

 Description   

In findAndModify's two phase protocol, change txn.run() to txn.runNoThrow() and handle all error cases for _clusterQueryWithoutShardkey & _clusterWriteWithoutShardKey.



 Comments   
Comment by Githook User [ 06/Jan/23 ]

Author:

{'name': 'Sanika Phanse', 'email': 'sanika.phanse@mongodb.com', 'username': 'sphanse99'}

Message: SERVER-71379 Ensure error propagation from internal transaction for all single write without shard key commands
Branch: master
https://github.com/mongodb/mongo/commit/24d3b65af21a007a6ec617cb1fc7d77905a103d6

Comment by Sanika Phanse (Inactive) [ 22/Dec/22 ]

Ensure 2 types of errors are propagated for findAndModify & for update/deleteOne:

  • Write Errors (for batch update & delete commands)
  • General Errors
Generated at Thu Feb 08 06:18:51 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.