[SERVER-72793] Handle WouldChangeOwningShard for bulkWrite Created: 12/Jan/23  Updated: 02/Feb/24  Resolved: 16/Nov/23

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

Type: Task Priority: Major - P3
Reporter: Lingzhi Deng Assignee: Kaitlin Mahar
Resolution: Fixed Votes: 0
Labels: milestone-2
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
causes SERVER-86120 Return write error on failure to comm... Open
causes SERVER-83416 Fix memory leak in bulkWrite handleWo... Closed
Related
is related to SERVER-82275 Support bulkWrite command in logic to... Backlog
Assigned Teams:
Replication
Backwards Compatibility: Fully Compatible
Sprint: Repl 2023-08-07, Repl 2023-09-04, Repl 2023-10-16, Repl 2023-10-30, Repl 2023-11-13, Repl 2023-11-27
Participants:

 Description   

If any operation returns WouldChangeOwningShard from a shard, mongos will handle it at the top-level after the entire bulkWrite has finished executing in the same way as handleWouldChangeOwningShardError, assuming this is a single-update bulkWrite. We do not support (i.e. error out) bulkWrite with ops size > 1 and updates that modify a document’s owning shard. This will be done in PM-2015.



 Comments   
Comment by Githook User [ 16/Nov/23 ]

Author:

{'name': 'Kaitlin Mahar', 'email': 'kaitlin.mahar@mongodb.com', 'username': 'kmahar'}

Message: SERVER-72793 Handle WouldChangeOwningShard errors for bulkWrite command
Branch: master
https://github.com/mongodb/mongo/commit/0fe2f7de906a39a7f49c47028cde6e15f02b6e75

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