[SERVER-39412] Continue to close connections when we enter rollback or removed state Created: 07/Feb/19  Updated: 29/Oct/23  Resolved: 11/Feb/19

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 4.1.8

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

Issue Links:
Gantt Dependency
has to be done before SERVER-38516 Remove “closeConnectionsOnStepdown” f... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Repl 2019-02-11, Repl 2019-02-25
Participants:

 Description   

The same code path is used for closing connections when we enter ROLLBACK or REMOVED as for stepping down. We need to separate them so that even after the "don't close connections on stepdown" project is done, we do continue to close connections on ROLLBACK and REMOVED.



 Comments   
Comment by Githook User [ 11/Feb/19 ]

Author:

{'name': 'Matthew Russotto', 'email': 'matthew.russotto@10gen.com', 'username': 'mtrussotto'}

Message: SERVER-39412 Continue to disconnect on rollback or on removal from the configuration.
Branch: master
https://github.com/mongodb/mongo/commit/8142ee91c63789c2899ab2bed6622ed2f72ed859

Comment by Matthew Russotto [ 07/Feb/19 ]

This is covered by the replsets/remove1.js test.

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