[SERVER-64004] Race condition in the TimeoutAbortsAwaitReplication leading the test to hang until timing out Created: 25/Feb/22  Updated: 29/Oct/23  Resolved: 01/Mar/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.0.0-rc0

Type: Bug Priority: Major - P3
Reporter: Mathis Bessa Assignee: Mathis Bessa
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Steps To Reproduce:

run the shard_split_donor_service_test unit test and change the 
shardSplitTimeoutMS in the `TimeoutAbortsAwaitReplication` to 100

Sprint: Server Serverless 2022-03-07
Participants:
Linked BF Score: 51

 Description   

It was found that there is a race condition on the windows environment that leads the test to hang forever waiting for the pauseShardSplitAfterBlocking fail point to be reached and instead the timeout happen and we go directly to the .onError step which hangs the test forever and the service is waiting for forget shard split command to be kicked in from the test which is currently blocking on the failpoint to be triggered. 



 Comments   
Comment by Githook User [ 28/Feb/22 ]

Author:

{'name': 'mathisbessamdb', 'email': 'mathis.bessa@mongodb.com', 'username': 'mathisbessamdb'}

Message: SERVER-64004 removing TimeoutAbortsAwaitReplication due to race condition and covered in cancelable_operation_context_test.cpp
Branch: master
https://github.com/mongodb/mongo/commit/d899515ce88922a540e7d77b904091866c67c4bc

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