TemporarilyUnavailable error escapes to the client on multi-document transaction

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • ALL
    • v5.3
    • Hide

      To reproduce consistently, lower the wiredTigerCacheSizeGB parameter to 0.25 and run:

      python buildscripts/resmoke.py run --suite=no_passthrough jstests/noPassthrough/multi_delete_in_transaction_large.js
      Show
      To reproduce consistently, lower the wiredTigerCacheSizeGB parameter to 0.25 and run: python buildscripts/resmoke.py run --suite=no_passthrough jstests/noPassthrough/multi_delete_in_transaction_large.js
    • Execution Team 2022-04-18
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      multi_delete_transaction_large.js sometimes returns a TemporarilyUnavailable error. This is not expected, since by design multi-doc transactions should return WriteConflict instead.

      Note that this test is different from most other test cases, because it generates a transaction consisting of >16MB worth of oplog statements, consequently generating two applyOps for the transaction.

            Assignee:
            Louis Williams
            Reporter:
            Josef Ahmad
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: