Details
-
Task
-
Resolution: Gone away
-
Major - P3
-
None
-
None
-
Sharding
Description
Currently, mongos can't attach the txnNumber from a request's operation context in the sharding_task_executor (like it does with the session id) because it can re-use the same operation context that sends the client's actual request to send metadata operations to the config server (e.g. implicitly creating a sharded collection through the ChunkManagerTargeter). If this could be resolved, mongos could blindly forward txnNumbers to mongod and let mongod validate them, instead of needing to do it itself.
Attachments
Issue Links
- is related to
-
SERVER-36260 Mongos should reject commands that aren't allowed in multi statement transactions by contain txnNumber
-
- Closed
-
- related to
-
SERVER-35829 Make router TransactionParticipant attach txnNumber to requests if not already there
-
- Closed
-
-
SERVER-36300 Audit re-use of operation contexts in mongos for metadata operations
-
- Closed
-