[SERVER-49938] Create Atlas workflow tests of what Atlas actually does today Created: 27/Jul/20  Updated: 29/Oct/23  Resolved: 15/Sep/20

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

Type: Task Priority: Major - P3
Reporter: Judah Schvimer Assignee: Xuerui Fa
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-45720 Create tests for Atlas Workflows Closed
is related to SERVER-47363 Define correct use of MemberIds in At... Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 2020-09-21
Participants:

 Description   

The tests created in SERVER-47363 were intended for this purpose, but then we made them aspirational of what we think is safest for users. While we figure out a simpler resync procedure, we should test both the procedure we recommend to users in our documentation, and the procedure Atlas actually does today. This may just mean running both the tests from before and after SERVER-47363, but we need to confirm what Atlas's behavior is today.



 Comments   
Comment by Githook User [ 15/Sep/20 ]

Author:

{'name': 'XueruiFa', 'email': 'xuerui.fa@mongodb.com', 'username': 'XueruiFa'}

Message: SERVER-49938: Create Atlas workflow tests of what Atlas actually does today
Branch: master
https://github.com/mongodb/mongo/commit/b3f2165c7cf7d2e4d098f86eaf8bfa3b87b683a1

Comment by Ralph Capasso [ 31/Jul/20 ]

judah.schvimer, SERVER-45720 looks good to me - one question / clarification - I am reviewing under the assumption that the test for replacing the node is replicating the process where we destroy the VM, and create a new node vs. re-syncing a node. When we re-sync the node, we do not set the votes to 0.

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