[SERVER-65109] TemporarilyUnavailable error escapes to the client on multi-document transaction Created: 31/Mar/22  Updated: 08/Apr/22  Resolved: 08/Apr/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Josef Ahmad Assignee: Louis Williams
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Duplicate
duplicates SERVER-65254 Disable TemporarilyUnavailableExcepti... Closed
Operating System: ALL
Backport Requested:
v5.3
Steps To Reproduce:

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

Sprint: Execution Team 2022-04-18
Participants:

 Description   

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.



 Comments   
Comment by Louis Williams [ 08/Apr/22 ]

Fixed by SERVER-65254.

Generated at Thu Feb 08 06:01:53 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.