Details
-
Bug
-
Resolution: Works as Designed
-
Major - P3
-
None
-
1.15.0
-
None
-
None
Description
When running a sharded transaction in a sharded cluster with a single mongos node, the session is not pinned to that server. Since topology scans may reveal additional mongos nodes, this can cause issues later. The session needs to be pinned even when running with a single mongos node.
I've also added a SPEC ticket to clarify this in the transaction spec: SPEC-1428.
Attachments
Issue Links
- links to