[SERVER-72782] SimulateCrash hook causes test connections to timeout Created: 12/Jan/23  Updated: 29/Oct/23  Resolved: 07/Feb/23

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

Type: Task Priority: Major - P3
Reporter: Haley Connelly Assignee: Gregory Wlodarek
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Assigned Teams:
Storage Execution
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2023-02-20
Participants:
Linked BF Score: 5

 Description   

SERVER-66673 increased the connection timeout for the SimulateCrash hook from 2 to 4 minutes. However, tests are still failing with connection timeout when it takes longer than 4 minutes to start up after an unclean shutdown.

We should decide if we want to further increase the connection timeout, or rethink the design of the hook.



 Comments   
Comment by Githook User [ 07/Feb/23 ]

Author:

{'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}

Message: SERVER-72782 Reduce SimulateCrash hook connection timeouts
Branch: master
https://github.com/mongodb/mongo/commit/713c60157fea0cab9da39ff90a8d0a8eb6583a1b

Comment by Louis Williams [ 17/Jan/23 ]

We should look into a solution to reduce the time it takes to restore from a crash:

  • CleanEveryN hook
  • Possibly tune the fuzzed parameters to reduce the amount of data between checkpoints
Generated at Thu Feb 08 06:22:47 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.