[SERVER-44460] reconfig.js should add last node back into config before stopping the test Created: 06/Nov/19  Updated: 29/Oct/23  Resolved: 12/Nov/19

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

Type: Bug Priority: Minor - P4
Reporter: William Schultz (Inactive) Assignee: William Schultz (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
related to SERVER-39172 Shut down mongod nodes in parallel in... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Repl 2019-11-18
Participants:
Linked BF Score: 21

 Description   

The jstests/replsets/reconfig.js does a force reconfig to remove the last node of a 5 node replica set and then calls ReplSetTest.stopSet. If the last node transitions to REMOVED state (because it received a heartbeat with the new config) while we are trying to validate collections on that node inside stopSet, we can run into an error because the node is not in primary or secondary state. Since the test has already finished testing the necessary aspects of reconfig by the end, we can add the node back into the set before stopping the test to avoid this issue.



 Comments   
Comment by Githook User [ 12/Nov/19 ]

Author:

{'username': 'will62794', 'email': 'william.schultz@mongodb.com', 'name': 'William Schultz'}

Message: SERVER-44460 Wait for node to be in REMOVED state in reconfig.js before stopping replica set
Branch: master
https://github.com/mongodb/mongo/commit/24b3ed65179d411aacac6b9f0fef1fa004857c85

Comment by William Schultz (Inactive) [ 06/Nov/19 ]

This underlying issue appears to have already existed before SERVER-39172, but I think those changes made it more likely since we now might do collection validation on a node much sooner after calling stopSet.

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