Mongos returns confusing error message if receives request with higher transaction number without 'startTransaction'

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Sharding
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Based on this conversation in the driver's spec for pinning a transaction to a single mongos, I found that mongos returns NoSuchTransaction if the mongos receives a request for a transaction number different from the last transaction number it had heard but without 'startTransaction'. Perhaps this error message can be more clear? I had assumed the error would be something like "cannot start new transaction unless 'startTransaction' is specified."

      There's a TODO in the code without a SERVER ticket, so I'm just filing this ticket to go back to it.

            Assignee:
            [DO NOT USE] Backlog - Sharding Team
            Reporter:
            Esha Maharishi (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: