Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-38420

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

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Sharding
    • Labels:
      None

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: