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

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Works as Designed
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Replication
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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().

            Assignee:
            [DO NOT USE] Backlog - Replication Team
            Reporter:
            Tess Avitabile (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: