-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Sharding
-
Fully Compatible
-
ALL
-
Sharding 2020-11-16
It is possible for a retryable write to be upconverted to a multi-document transaction when a document's shard key value is being modified and would change owning shards. The resulting config.transactions record must be migrated to the recipient shard to prevent the retryable write from being re-executed as a retryable write. The retryable write is instead expected to fail with an IncompleteTransactionHistory error response.
The {state: {$exists: false}} filter was removed from session_catalog_migration_source.cpp as part of SERVER-40475 after being added by SERVER-38844. It should be similarly removed from createConfigTxnCloningPipelineForResharding().
- is related to
-
SERVER-38844 SessionMigrationSource should explicitly ignore config.transactions entry meant for transactions
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-