-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Fully Compatible
-
Sharding 2021-12-13, Sharding 2021-12-27, Sharding 2022-01-10, Sharding 2022-01-24, Sharding 2022-02-07, Sharding 2022-02-21, Sharding 2022-03-07
-
9
-
8
- Make mongos use internal transaction API for handling WouldChangeOwningShard errors (only for FCV 6.0)
- Support handling the errors for all session option configurations and batch size
- ** Handle unordered/ordered batch writes-
- depends on
-
SERVER-58760 [API] Make internal transaction API support distributed transactions
- Closed
- is depended on by
-
SERVER-60532 [Upgrade/downgrade] Make mongos fallback to previous way of handling WouldChangingOwningShard when internal transactions are not supported
- Backlog
-
SERVER-58762 Add a concurrency workload that runs operations that fail with WouldChangeOwningShard errors concurrently with chunk migrations
- Closed
-
SERVER-59566 Retry and timeout policy for internal transactions
- Closed
- related to
-
SERVER-64052 Implement unstash for TransactionRouter
- Closed
-
SERVER-64070 Clean up startTransaction handling for transaction API in client transaction case
- Closed
-
SERVER-64540 Add feature flag just for using txn API for updating document shard key value
- Closed
- split to
-
SERVER-62080 Make read and write concern configurable for internal transaction API
- Closed
-
SERVER-62516 Return commit result from internal transaction API
- Closed
-
SERVER-62519 Internal transaction API should abort between transient error retries
- Closed
-
SERVER-63364 Use transaction API to handle WCOS errors for findAndModify without retryability
- Closed
-
SERVER-63366 Basic retryability support for findAndModify WCOS with transaction API
- Closed
-
SERVER-63746 Handle client session case for transaction API
- Closed
-
SERVER-63747 Handle client retryable write case on mongod for transaction API
- Closed