[SERVER-73523] Rephrase establish_cursors unittest InterruptedWithDanglingRemoteRequest to avoid failpoint Created: 01/Feb/23 Updated: 29/Oct/23 Resolved: 06/Feb/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.3.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | George Wangensteen | Assignee: | George Wangensteen |
| 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: | Service Arch 2023-02-06, Service Arch 2023-02-20 | ||||||||
| Participants: | |||||||||
| Description |
|
One of the establish cursors unittests uses a failpoint that intercepts requests being scheduled by the ARS to ensure that a request to a particular HostAndPort hangs before being scheduled on the mock network interface. Now that we're pushing host-and-ort targeting down to a layer below the ARS and rephrasing the ARS internals, we need to rewrite this test. The purpose of the test is to ensure that after establishCursors has recieved one successful response from the ARS, but one response is still dangling when the opCtx is interrupted, establishcCursors sends 2 _killOperations (one to each host) to clean up cursors. |
| Comments |
| Comment by Githook User [ 03/Feb/23 ] |
|
Author: {'name': 'George Wangensteen', 'email': 'george.wangensteen@mongodb.com', 'username': 'gewa24'}Message: |