[SERVER-41234] Concurrent step downs due to step down via heartbeat and force reconfig should ensure that the term maintained by topology coordinator is set to TopologyCoordinator::_pendingTermUpdateDuringStepDown. Created: 19/May/19  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: Suganthi Mani 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:
Backports
Related
related to SERVER-37574 Force reconfig should kill user opera... Closed
Assigned Teams:
Replication
Backport Requested:
v4.0, v3.6
Participants:

 Description   

Force reconfig cmd and force reconfig via heartbeat should be able to take care of updating the term & resetting _pendingTermUpdateDuringStepDown (like we do it in unconditional step down) if they cause step down and _pendingTermUpdateDuringStepDown is set.

This is a 4.0 bug and the fix must be backported.

 

 Consequence of this bug is that this requires another heartbeat or metadata update (e.g.. during oplog fetching) to update the term again. (see SERVER-28290).


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