Always return TransactionTooLarge rather than BSONObjectTooLarge when transaction is too large to fit in a single applyOps

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.0.11
    • Affects Version/s: 4.0.9
    • Component/s: None
    • None
    • Fully Compatible
    • Repl 2019-07-01, Repl 2019-07-15
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      We should backport the moving of the try clause in onTransactionCommit up to also cover the opsArray.done() call since it is possible for that call to throw a BSONObjectTooLarge exception, as we do in SERVER-40790.

      The call in question on the 4.0 branch is here: https://github.com/mongodb/mongo/blob/ed33d2f8e66cd907ef13ee162f6a1dac3ff25672/src/mongo/db/op_observer_impl.cpp#L918

            Assignee:
            Siyuan Zhou
            Reporter:
            Jason Chan
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: