[SERVER-36960] Stepdown thread should handle AutoReconnect exceptions when executing replSetStepUp Created: 31/Aug/18  Updated: 29/Oct/23  Resolved: 24/Apr/20

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: 4.7.0

Type: Bug Priority: Major - P3
Reporter: Jonathan Abrahams Assignee: Mikhail Shchatko
Resolution: Fixed Votes: 0
Labels: neweng, stm, tig-resmoke
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
is related to SERVER-36997 Stepdown thread should perform w:all ... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: STM 2020-05-04
Participants:
Linked BF Score: 12
Story Points: 2

 Description   

The stepdown thread can terminate when issuing a replSetStepUp command, as stepdown.py does not handle AutoReconnect exceptions.



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

Author:

{'name': 'Mikhail Shchatko', 'email': 'mikhail.shchatko@mongodb.com'}

Message: SERVER-36960 Stepdown thread should handle AutoReconnect exceptions when executing replSetStepUp
Branch: master
https://github.com/mongodb/mongo/commit/74ac57a2f6ca120294592237d547a665513cc52d

Comment by Jonathan Abrahams [ 07/Sep/18 ]

It's still possible for this condition to occur, even if SERVER-36997 is implemented.

Comment by Jonathan Abrahams [ 07/Sep/18 ]

It's possible for a replSetStepUp to fail with AutoReconnect if that node goes into Rollback (which causes it to close any open connections).

Comment by Max Hirschhorn [ 01/Sep/18 ]

jonathan.abrahams, I wouldn't expect a network error to occur as a result of running the replSetStepUp command. Do you have more context on why the AutoReconnect exception occurred?

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