[SERVER-65825] Increase fassertOnLockTimeoutForStepUpDown default timeout to 30 seconds Created: 20/Apr/22  Updated: 29/Oct/23  Resolved: 21/Apr/22

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

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

Issue Links:
Backports
Depends
Related
is related to SERVER-56756 Primary cannot stepDown when experien... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v6.0
Participants:
Linked BF Score: 137

 Description   

This is to avoid conflicting with the existing behavior where a node will crash in 30 seconds if it fails to write to a config server as part of stepUp.



 Comments   
Comment by Githook User [ 20/Apr/22 ]

Author:

{'name': 'Jason Chan', 'email': 'jason.chan@mongodb.com', 'username': 'jasonjhchan'}

Message: SERVER-65825 Increase fassertOnLockTimeoutForStepUpDown default timeout to 30 seconds

(cherry picked from commit 7001f53ea533b5ca6a7b5bf904a80bb18611523f)
Branch: v6.0
https://github.com/mongodb/mongo/commit/8c438c6c733b3a79236cf578da8e24d9b26881bf

Comment by Githook User [ 20/Apr/22 ]

Author:

{'name': 'Jason Chan', 'email': 'jason.chan@mongodb.com', 'username': 'jasonjhchan'}

Message: SERVER-65825 Increase fassertOnLockTimeoutForStepUpDown default timeout to 30 seconds
Branch: master
https://github.com/mongodb/mongo/commit/7001f53ea533b5ca6a7b5bf904a80bb18611523f

Generated at Thu Feb 08 06:03:44 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.