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

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

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 4.0.9
    • Fix Version/s: 4.0.11
    • Component/s: None
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Sprint:
      Repl 2019-07-01, Repl 2019-07-15

      Description

      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

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: