[SERVER-76099] Handle NoSuchTransaction errors in fle2_crud.js Created: 13/Apr/23 Updated: 29/Oct/23 Resolved: 01/May/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Erwin Pe | Assignee: | Erwin Pe |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Security 2023-04-17, Security 2023-05-01 | ||||
| Participants: | |||||
| Linked BF Score: | 16 | ||||
| Description |
|
Too much contention in the server when performing QE reads can cause the internal transactions to exceed the retry limit of 120 and return a NoSuchTransaction error. Because of this, the fle2_crud.js FSM test may fail when many worker threads are performing "findOne" in the readDocs phase. So, to stop the test from terminating when it hits this transient error, the test must be fixed so that a worker thread can catch the NoSuchTransaction error and back off for a few seconds before retrying the read. |