-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Query Execution
-
None
-
None
-
None
-
None
-
None
-
None
-
None
this ticket is purely moving where we catch handleWouldChangeOwningShard into the UnifiedWriteExecutor.
optimistically trying to detect in the router that it would change ownership and potentially having the first try in a transaction is out of scope for this ticket
- depends on
-
SERVER-114991 UWE should handle upserts that would change owning shard correctly
-
- Backlog
-
-
SERVER-114993 UWE should add context about orphans for would change owning shard updates that fail with duplicate key error
-
- Backlog
-
-
SERVER-114994 add support to UWE to handle find and modify commands that would change owning shard
-
- Backlog
-
-
SERVER-114995 UWE should not attempt to handle more than 1 WouldChangeOwningShardError per client command
-
- Backlog
-
-
SERVER-114997 simplify UWE would change owning shard "already in transaction" logic with helper
-
- Backlog
-
-
SERVER-114998 make sure UWE is resilient to concurrent collection drops while executing a shard key update
-
- Backlog
-
-
SERVER-115271 Support WCOS in UWE when 'featureFlagTimeseriesUpdatesSupport' is enabled
-
- Backlog
-
-
SERVER-115272 Investigate 'oneShard' metric failure in 'jstests/noPassthrough/crud/bulk_write_metrics.js' with WCOS writes
-
- Backlog
-
- is duplicated by
-
SERVER-104122 Support for 'WouldChangeOwningShard' writes in UWE
-
- Closed
-
- is related to
-
SERVER-104122 Support for 'WouldChangeOwningShard' writes in UWE
-
- Closed
-
- related to
-
SERVER-114190 Complete TODO listed in SERVER-103146
-
- Closed
-