[SERVER-72780] s_query_test ResultsMergerTestFixture.ShouldBeInterruptibleDuringBlockingNext can hang Created: 12/Jan/23 Updated: 29/Oct/23 Resolved: 18/Jan/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.3.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Ivan Fefer | Assignee: | Ivan Fefer |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Sprint: | QE 2023-01-23 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 5 | ||||||||||||||||
| Description |
|
Sometimes in evergreen s_query_test fails from timeout on ResultsMergerTestFixture.ShouldBeInterruptibleDuringBlockingNext. Locally this test is always successful, but if we run stress -c <number of cpu cores> in parallel with the s_query_test, it will hang reliably |
| Comments |
| Comment by Ivan Fefer [ 18/Jan/23 ] |
|
Test failed because AsyncResultsMerger didn't send kill commands to interrupted cursors, which tests expected to see and test just waited for it indefinitely. We discussed that this is a good idea to explicitly kill interrupted cursors as long as we "fire and forget" the request. |
| Comment by Githook User [ 17/Jan/23 ] |
|
Author: {'name': 'Ivan Fefer', 'email': 'ivan.fefer@mongodb.com', 'username': 'Fefer-Ivan'}Message: |