-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Replication
-
Fully Compatible
-
Repl 2023-08-07, Repl 2023-09-04, Repl 2023-10-16, Repl 2023-10-30, Repl 2023-11-13, Repl 2023-11-27
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.
- causes
-
SERVER-83416 Fix memory leak in bulkWrite handleWouldChangeOwningShardError
- Closed
-
SERVER-86120 Return write error on failure to commit txn for retryable update that modifies doc shard key
- Closed
- is related to
-
SERVER-82275 Support bulkWrite command in logic to handle WouldChangeOwningShard errors via internal transactions
- Backlog