TransactionRouter should not assert that a participant's readOnly flag is set if the transaction is being aborted

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.1.14
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • ALL
    • Sharding 2019-06-03
    • 28
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Because the client is allowed to send abortTransaction after getting back an error from an earlier statement, and besides, many of our tests do this.

            Assignee:
            Alexander Taskov (Inactive)
            Reporter:
            Esha Maharishi (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: