Transactions fail with TransactionTooLarge instead of generating multiple applyOps

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 6.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • Hide 
      db.c.insertMany([...Array(400000).keys()].map(x => ({_id: x})));
const session = db.getMongo().startSession();
const coll = session.getDatabase('test').c
session.startTransaction();coll.deleteMany({_id: {$gte: 0}});
session.commitTransaction();
      Show
      db.c.insertMany([...Array(400000).keys()].map(x => ({_id: x}))); const session = db.getMongo().startSession(); const coll = session.getDatabase('test').c session.startTransaction();coll.deleteMany({_id: {$gte: 0}}); session.commitTransaction();
    • QE 2022-04-04
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      SERVER-62785 introduced a regression that fails transactions which would previously succeed and generate multiple applyOps entries. The regression can be reproduced deleting a large amount of small documents in a single transaction such that the committed operation would span across multiple applyOps.

            Assignee:
            Mindaugas Malinauskas
            Reporter:
            Josef Ahmad
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: