[SERVER-45081] Increment the config term via reconfig on step-up Created: 12/Dec/19  Updated: 29/Oct/23  Resolved: 03/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: Siyuan Zhou Assignee: Siyuan Zhou
Resolution: Fixed Votes: 0
Labels: safe-reconfig-consensus
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
Related
is related to SERVER-47119 Config term does not get initialized ... Closed
is related to SERVER-46987 Blacklist tests using waitForConfigRe... Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 2020-01-27, Repl 2020-02-10, Repl 2020-02-24, Repl 2020-03-09
Participants:
Linked BF Score: 42

 Description   

Update its “term” field of config on step-up unless it’s force reconfig in term -1



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

Author:

{'name': 'Siyuan Zhou', 'username': 'visualzhou', 'email': 'siyuan.zhou@mongodb.com'}

Message: SERVER-45081 Add a unit test case for awaitable isMaster after stepup and config term increment.
Branch: master
https://github.com/mongodb/mongo/commit/61865d1617e39506c9e0c9202ba2bb50217c7c1e

Comment by Githook User [ 03/Mar/20 ]

Author:

{'name': 'Siyuan Zhou', 'username': 'visualzhou', 'email': 'siyuan.zhou@mongodb.com'}

Message: SERVER-45081 Increment config term via reconfig on stepup.
Branch: master
https://github.com/mongodb/mongo/commit/07302cd28d7dce013f9df1ba2f5fcf70e506bce5

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