[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:
Backports
Depends
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: SERVER-48409 Fix race in establishCursors unittest
Branch: v4.4
https://github.com/mongodb/mongo/commit/c89c6eca4583203ff7bd8076f1c55cb00b0332b9

Comment by Githook User [ 09/Jun/20 ]

Author:

{'name': 'David Percy', 'email': 'david.percy@mongodb.com', 'username': 'dpercy'}

Message: SERVER-48409 Fix race in establishCursors unittest
Branch: master
https://github.com/mongodb/mongo/commit/6eae2c14a0259c0d54b25c3ec2aa513bdca2c818

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