[SERVER-32136] initial_sync_drop_collection.js should wait for system to stablize after restarting node Created: 01/Dec/17  Updated: 30/Oct/23  Resolved: 05/Dec/17

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 3.6.2, 3.7.1

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:
Backports
Depends
Related
is related to SERVER-31267 CollectionCloner fails if collection ... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:
Linked BF Score: 0

 Comments   
Comment by Githook User [ 03/Jan/18 ]

Author:

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

Message: SERVER-32136 initial_sync_drop_collection.js should wait for system to stabilize after restarting node.

(cherry picked from commit 5be8810c5df9c98966cee6539220ebc7b38bf4c8)
Branch: v3.6
https://github.com/mongodb/mongo/commit/a6a3056ce0833e969665380e0eca7ed2aca42742

Comment by Githook User [ 05/Dec/17 ]

Author:

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

Message: SERVER-32136 initial_sync_drop_collection.js should wait for system to stabilize after restarting node.
Branch: master
https://github.com/mongodb/mongo/commit/5be8810c5df9c98966cee6539220ebc7b38bf4c8

Comment by Matthew Russotto [ 01/Dec/17 ]

It also makes sense to set the secondaries to priority 0 to ensure the election comes out the way we like.

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