[SERVER-28969] Wait until the voter has the latest optime in case 3 of catchup.js Created: 25/Apr/17  Updated: 30/Oct/23  Resolved: 27/Apr/17

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

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

Issue Links:
Backports
Depends
Related
related to SERVER-26848 Exit catchup mode when not syncing mo... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v3.4
Sprint: Repl 2017-05-08
Participants:
Linked BF Score: 0

 Description   

Chances are the heartbeats to the disconnected primary come back earlier than those to the voter, so that the new primary doesn't realize the voter has newer data and exits catchup mode prematurely.



 Comments   
Comment by Githook User [ 16/Jun/17 ]

Author:

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

Message: SERVER-28969 Wait until the voter has the latest optime in case 3 of catchup.js

(cherry picked from commit 6626128371d5f56cfae1079d0d67ec675f06bb84)
Branch: v3.4
https://github.com/mongodb/mongo/commit/1b5e99525f78b0e88eac7dd8663d44d543195803

Comment by Githook User [ 27/Apr/17 ]

Author:

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

Message: SERVER-28969 Wait until the voter has the latest optime in case 3 of catchup.js
Branch: master
https://github.com/mongodb/mongo/commit/6626128371d5f56cfae1079d0d67ec675f06bb84

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