[SERVER-82275] Support bulkWrite command in logic to handle WouldChangeOwningShard errors via internal transactions Created: 17/Oct/23  Updated: 17/Nov/23

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

Type: Task Priority: Major - P3
Reporter: Kaitlin Mahar Assignee: Backlog - Cluster Scalability
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-72793 Handle WouldChangeOwningShard for bul... Closed
Assigned Teams:
Cluster Scalability
Participants:

 Description   

We have logic which is guarded behind the (currently disabled by default and untested) FeatureFlagUpdateDocumentShardKeyUsingTransactionApi to handle changing a document's owning shard with the internal transaction API.

Once we move toward testing and enabling that flag, this logic will need to be updated to work for the bulkWrite command as well. (SERVER-72793 covers updating the legacy WCOS logic to work for bulkWrite.)



 Comments   
Comment by Kaitlin Mahar [ 12/Nov/23 ]

It would be good to consider executing the delete+insert using the bulkWrite command in the case that WCOS is encountered in a bulkWrite, rather than using the delete and insert commands. 

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