[SERVER-27911] Merge all stepdown code paths Created: 03/Feb/17  Updated: 06/Dec/22  Resolved: 13/Dec/19

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

Type: Improvement Priority: Major - P3
Reporter: Siyuan Zhou Assignee: Backlog - Replication Team
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-27555 ReplicationCoordinatorImpl::_memberSt... Closed
related to SERVER-28290 stepping down due to a higher term se... Closed
related to SERVER-27892 Clarify locking rules for _canAcceptN... Closed
related to SERVER-31277 Cancel all user operations on heartbe... Closed
is related to SERVER-34581 Merge reconfig code paths Backlog
Assigned Teams:
Replication
Sprint: Repl 2017-03-06, Repl 2017-03-27, Repl 2017-04-17, Repl 2017-05-08, Repl 2017-05-29, Repl 2017-06-19, Repl 2017-07-31, Repl 2017-08-21, Repl 2017-09-11, Repl 2017-10-02, Repl 2017-10-23
Participants:

 Description   

The code path of stepdown due to higher term differs from the code path of stepdown command. We need to consolidate them.



 Comments   
Comment by Judah Schvimer [ 22/Jan/19 ]

This includes force reconfig stepdown and force reconfig heartbeat stepdown.

Comment by Benety Goh [ 10/Mar/17 ]

A step down due to higher term currently does not retain the higher term. This requires another heartbeat or metadata update (e.g.. during oplog fetching) to update the term again.

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