Session is not pinned when only a single mongos is present

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Works as Designed
    • Priority: Major - P3
    • None
    • Affects Version/s: 1.15.0
    • Component/s: None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            Unassigned
            Reporter:
            Andreas Braun
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: