Error when aborting/committing a nonexistent txn or starting a txn with one running

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.0.0-rc0
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • Repl 2018-04-23, Repl 2018-05-07, Repl 2018-05-21
    • 28
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      For example, right now if you start a transaction, then start another transaction, the shell allows that. Drivers will raise an error.

      We should also error when abortTransaction or commitTransaction is called when no transaction is running on the current session.

            Assignee:
            Pavithra Vetriselvan
            Reporter:
            Spencer Brody (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: