[SERVER-28290] stepping down due to a higher term seen in a heartbeat should not discard term after stepdown Created: 13/Mar/17  Updated: 29/Jan/18  Resolved: 12/Jan/18

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

Type: Bug Priority: Major - P3
Reporter: Benety Goh Assignee: Siyuan Zhou
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Related
related to SERVER-31330 Stepping down while exiting drain mod... Closed
is related to SERVER-26746 Nodes should update their own term fr... Closed
is related to SERVER-27911 Merge all stepdown code paths Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v3.6
Sprint: 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, Repl 2018-01-15, Repl 2018-01-29
Participants:
Linked BF Score: 0

 Description   

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.



 Comments   
Comment by Githook User [ 26/Jan/18 ]

Author:

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

Message: SERVER-28290 Stepping down due to a higher term seen in a heartbeat should not discard term after stepdown.

(cherry picked from commit f496011618ba7b1a99e6d9e51bea6966341cfd12)
Branch: v3.6
https://github.com/mongodb/mongo/commit/762a01d343800cb1c3d1293e6bcf7941d9d13223

Comment by Githook User [ 12/Jan/18 ]

Author:

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

Message: SERVER-28290 Stepping down due to a higher term seen in a heartbeat should not discard term after stepdown.
Branch: master
https://github.com/mongodb/mongo/commit/f496011618ba7b1a99e6d9e51bea6966341cfd12

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