[SERVER-48409] Fix race in establishCursors unittest Created: 26/May/20 Updated: 29/Oct/23 Resolved: 09/Jun/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.4.0-rc11, 4.7.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | David Percy | Assignee: | David Percy |
| 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 | ||||||||
| Backport Requested: |
v4.4
|
||||||||
| Participants: | |||||||||
| Linked BF Score: | 0 | ||||||||
| Description |
|
In establish_cursors_test.cpp, InterruptedWithDanglingRemoteRequest has been occasionally hanging. It looks like a bug in the test: if establishCursors gets responses from both shards before it sees that its opCtx is killed, it's allowed to return successfully instead of throwing and cleaning up. I think we need a second failpoint, to ensure the test marks the opCtx as killed before establishCursors does its check. |
| Comments |
| Comment by Githook User [ 21/Jun/20 ] |
|
Author: {'name': 'David Percy', 'email': 'david.percy@mongodb.com', 'username': 'dpercy'}Message: |
| Comment by Githook User [ 09/Jun/20 ] |
|
Author: {'name': 'David Percy', 'email': 'david.percy@mongodb.com', 'username': 'dpercy'}Message: |