[SERVER-45997] Test re-sync cases where nodes can roll back majority committed writes Created: 05/Feb/20  Updated: 29/Oct/23  Resolved: 04/Mar/20

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

Type: Task Priority: Major - P3
Reporter: Judah Schvimer Assignee: Vesselina Ratcheva (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-17934 Do not report upstream progress while... Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 2020-02-24, Repl 2020-03-09
Participants:

 Description   

Test that acknowledging progress while in initial sync, fixed in SERVER-17934, no longer can lead to rolling back majority committed writes.
Test that by resyncing a node against a member in a minority that does not contain a write the resyncing node originally helped commit, a set can lose majority writes, as expected.



 Comments   
Comment by Githook User [ 04/Mar/20 ]

Author:

{'name': 'Vesselina Ratcheva', 'username': 'vessy-mongodb', 'email': 'vesselina.ratcheva@10gen.com'}

Message: SERVER-45997 Test resyncing a majority member against a minority node
Branch: master
https://github.com/mongodb/mongo/commit/35a5d455672e65127a24e7cdb98ea1472124af4a

Comment by Githook User [ 02/Mar/20 ]

Author:

{'name': 'Vesselina Ratcheva', 'username': 'vessy-mongodb', 'email': 'vesselina.ratcheva@10gen.com'}

Message: SERVER-45997 Fix optimes check in no_progress_updates_during_initial_sync.js
Branch: master
https://github.com/mongodb/mongo/commit/933539d9cf046e1803718f998e95abcc1ec960f9

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