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

readConcern parse failure on start of multi-statement transaction should immediately abort transaction

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Works as Designed
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Replication
    • None
    • Replication

    Description

      If the readConcern specified on the first statement fails to parse, we return an error, but leave the transaction open and _txnResourceStash empty. When we receive another operation in the same transaction, we find that _txnResourceStash is empty and abort the transaction, returning NoSuchTransaction. It would be preferable to immediately abort the transaction when readConcern fails to parse. Similarly for other errors encountered prior to unstashTransactionResources().

      Attachments

        Activity

          People

            backlog-server-repl Backlog - Replication Team
            tess.avitabile@mongodb.com Tess Avitabile (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: