[SERVER-26748] Don't call for priority takeover when repl lagged Created: 24/Oct/16  Updated: 25/Jan/17  Resolved: 01/Nov/16

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 3.2.11, 3.4.0-rc3

Type: Improvement Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Spencer Brody (Inactive)
Resolution: Done Votes: 0
Labels: code-and-test
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Documented
is documented by DOCS-9475 Docs for SERVER-26748: Don't call for... Closed
Related
related to SERVER-27056 Don't enforce data freshness for step... Closed
is related to SERVER-26725 Automatically reconfig pv1 replica se... Closed
Backwards Compatibility: Minor Change
Backport Completed:
Sprint: Repl 2016-11-21
Participants:

 Description   

Currently in pv1 we call for priority takeover without concern for whether the higher priority node is caught up in replication, which can lead to unnecessary rollbacks of w:1 writes. If we avoid calling for an election due to priority takeover if we are more than X seconds repl lagged, then that in combination with the catchup period should prevent any writes from being lost during priority takeover.



 Comments   
Comment by Githook User [ 07/Nov/16 ]

Author:

{u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}

Message: SERVER-26748 Don't call for priority takeover when repl lagged.

Backport of 286a682a5ecff2e1646cbe68315529f7b3f6bd7c
Branch: v3.2
https://github.com/mongodb/mongo/commit/c3e843b10cd3522fd5f5db71486cfc738c88428d

Comment by Spencer Brody (Inactive) [ 01/Nov/16 ]

This work introduced a new startup-only setParameter, priorityTakeoverFreshnessWindowSeconds, which controls how up-to-date a secondary must be to call for priority takeover.

Comment by Githook User [ 01/Nov/16 ]

Author:

{u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}

Message: SERVER-26748 Fix message when not fresh enough to call for priority takeover
Branch: master
https://github.com/mongodb/mongo/commit/3bcb50a925c7d1d24ffd520ea0fdfad54bf44d57

Comment by Githook User [ 01/Nov/16 ]

Author:

{u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}

Message: SERVER-26748 Don't call for priority takeover when repl lagged.
Branch: master
https://github.com/mongodb/mongo/commit/286a682a5ecff2e1646cbe68315529f7b3f6bd7c

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