[SERVER-23663] New primary syncs from chosen node to catch up with timeout Created: 12/Apr/16  Updated: 25/Jan/17  Resolved: 05/Aug/16

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 3.3.11

Type: Task Priority: Major - P3
Reporter: Crystal Horn Assignee: Siyuan Zhou
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
is documented by DOCS-9519 Docs for SERVER-23663: New primary sy... Closed
Duplicate
is duplicated by SERVER-22502 Replication Protocol 1 rollbacks are ... Closed
is duplicated by SERVER-18453 Avoiding Rollbacks in new Raft based ... Closed
Related
related to SERVER-26394 prohibit choosing ourselves as a sync... Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 15 (06/03/16), Repl 16 (06/24/16), Repl 17 (07/15/16), Repl 18 (08/05/16)
Participants:
Case:

 Description   

To avoid unnecessary rollback after a PV1 election, the new primary finds the node with the highest lastOpTime, then tries to sync all the oplog from that node to catch up its opTime. This ticket is for the catch-up phase.

If the catch-up timeout expires before we exhaust all the sync source’s oplog entries, the new primary ends the catch-up phase and proceeds to exit drain mode like normal.
If the query from the remote node fails, treat the same as if the catch-up timeout expired. Do not attempt to choose a new sync source.



 Comments   
Comment by Githook User [ 05/Aug/16 ]

Author:

{u'username': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}

Message: SERVER-23663 fix lint
Branch: master
https://github.com/mongodb/mongo/commit/0a8a7fa7da1a8bbe31b9eb8a0ca8be6927d7139c

Comment by Githook User [ 04/Aug/16 ]

Author:

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

Message: SERVER-23663 New primary syncs from chosen node to catch up with timeout

SERVER-23662 Implement "catch-up timeout" configuration variable
Branch: master
https://github.com/mongodb/mongo/commit/953a241f6dd1541905a1b6e259140635b80238de

Comment by Githook User [ 02/Aug/16 ]

Author:

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

Message: SERVER-23663 Add option to wait for durable optime to awaitReplication()
Branch: master
https://github.com/mongodb/mongo/commit/110f7bd612bf944848c448547d098786255ae6ae

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