[SERVER-62653] Non hermitic test commit_prepared_transaction_errors.js should retry Created: 14/Jan/22  Updated: 11/May/23  Resolved: 11/May/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 5.3.0, 5.0.5, 5.1.1
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Andrew Shuvalov (Inactive) Assignee: Lamont Nelson
Resolution: Won't Do Votes: 0
Labels: sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Operating System: ALL
Participants:
Linked BF Score: 19

 Description   

As mentioned in referenced BF is experiencing the very rare race when `WiredTigerIdIndex::_insert()` failed with WriteConflict error. The failure happens approximately once per month and only on in-memory fixtures. The WriteConflict is not expected, however it's legal, there is no consistency error and the error message clearly says: "Please retry your operation or multi-document transaction."

Most likely, the cause of this failure is non-hermetic test rather than a real bug. The action taken should not change the strength of the test correction and should verify that the race is brief and not persistent.

What we need to verify is that the test should pass after a short retry, we must ensure that the retry succeeds and the WriteConflict is transient. I think it's better to retry just the failed test case instead of the whole suite.


Generated at Thu Feb 08 05:55:42 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.