[SERVER-29844] If node has a higher priority than the primary and is the most up to date, schedule the takeover that will execute faster. Created: 23/Jun/17  Updated: 30/Oct/23  Resolved: 22/Jan/18

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

Type: Task Priority: Major - P3
Reporter: Samyukta Lanka Assignee: Pavithra Vetriselvan
Resolution: Fixed Votes: 0
Labels: PM-783, neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Backwards Compatibility: Fully Compatible
Backport Requested:
v3.6
Sprint: Repl 2017-12-04, Repl 2017-12-18
Participants:

 Description   

If the node is eligible for both a priority takeover and a catchup takeover, we currently prefer the catchup takeover. However, if the node has a higher priority than the current primary and is the most up-to-date in the entire set, it is safe to call whichever takeover will happen sooner.



 Comments   
Comment by Githook User [ 29/May/18 ]

Author:

{'username': 'pvselvan', 'name': 'Pavithra Vetriselvan', 'email': 'pavithra.vetriselvan@mongodb.com'}

Message: SERVER-29844 Prefers a priority takeover if the current node has highest priority and it is most up to date

(cherry picked from commit 40dc86136f85f88e1782a1c65b49bfba02757009)
Branch: v3.6
https://github.com/mongodb/mongo/commit/9eb61dea52f7520089419dc98eda8ca8190cca5c

Comment by Gregory McKeon (Inactive) [ 22/Jan/18 ]

william.schultz we did this, right? Can we resolve with a 3.7.1 fixVersion?

Comment by Githook User [ 05/Dec/17 ]

Author:

{'email': 'pavithra.vetriselvan@mongodb.com', 'name': 'Pavithra Vetriselvan'}

Message: SERVER-29844 Prefers a priority takeover if the current node has highest priority and it is most up to date
Branch: master
https://github.com/mongodb/mongo/commit/40dc86136f85f88e1782a1c65b49bfba02757009

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