-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication, Sharding
-
None
-
Fully Compatible
-
Sharding EMEA 2022-04-18, Sharding EMEA 2022-05-02, Sharding EMEA 2022-05-16, Sharding EMEA 2022-05-30
The code introduced in SERVER-62581 was taking care of direct inserts to shards but we forgot to cover the case in which those inserts are part of a transaction. It looks like under that scenario we take a different insert path
antonio.fuschetto@mongodb.com discovered that the problem is not just for TXN doing inserts but for TXN doing any op BUT always directly against the shard, without going through the mongos).
- depends on
-
SERVER-65859 Enable filtering of change steam events for individual statements of transactions
- Closed
-
SERVER-65858 Mark the applyOps entries when the operations involves orphaned documents
- Closed