[SERVER-45096] Test safe reconfig never rolls back entries committed in earlier configs. Created: 12/Dec/19  Updated: 29/Oct/23  Resolved: 17/Mar/20

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 4.4.0-rc0, 4.7.0

Type: Task Priority: Major - P3
Reporter: Siyuan Zhou Assignee: William Schultz (Inactive)
Resolution: Fixed Votes: 0
Labels: safe-reconfig-testing
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Related
is related to SERVER-45088 Test safe reconfig avoids diverging c... Closed
is related to SERVER-46742 Factor out logic to wait for config c... Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v4.4
Sprint: Repl 2020-02-24, Repl 2020-03-09, Repl 2020-03-23
Participants:

 Description   

Targeted unit tests for known cases that break the existing protocol:

  • Rolling back committed entries (fixed by Oplog Commitment). Test that a new config succeeds only after the data committed in the previous config are also committed in the current config.
    • Test the previous reconfig happens before the primary’s election
    • Test the previous reconfig happens after the primary’s election


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

Author:

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

Message: SERVER-45096 Add unit tests to ensure safe reconfig never rolls back entries committed in earlier configs

(cherry picked from commit 5d9752bd42803be61b519bb41a30e73c308b7853)
Branch: v4.4
https://github.com/mongodb/mongo/commit/5dd4f975d7db7d29633bd9530a0cf4a1c094542f

Comment by Githook User [ 17/Mar/20 ]

Author:

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

Message: SERVER-45096 Add unit tests to ensure safe reconfig never rolls back entries committed in earlier configs
Branch: master
https://github.com/mongodb/mongo/commit/5d9752bd42803be61b519bb41a30e73c308b7853

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