[SERVER-26572] Reset stopTimestamp in DataReplicator when initial sync apply phase tries to fetch a remote document Created: 11/Oct/16  Updated: 31/Oct/16  Resolved: 26/Oct/16

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

Type: Bug Priority: Major - P3
Reporter: Judah Schvimer Assignee: Judah Schvimer
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Repl 2016-10-31
Participants:

 Description   

When the oplog applier fetches a document from our sync source, we must get the latest optime from the sync source, and set that as our stopTimestamp. That way we will not finish initial sync until our data is all from a consistent point.



 Comments   
Comment by Githook User [ 26/Oct/16 ]

Author:

{u'username': u'judahschvimer', u'name': u'Judah Schvimer', u'email': u'judah@mongodb.com'}

Message: SERVER-26572 move fetchCount to DataReplicator
Branch: master
https://github.com/mongodb/mongo/commit/67994f33a88f4aa70283e155c75f48ce997ccdc3

Comment by Githook User [ 19/Oct/16 ]

Author:

{u'username': u'judahschvimer', u'name': u'Judah Schvimer', u'email': u'judah@mongodb.com'}

Message: SERVER-26572 Reset stopTimestamp in DataReplicator when initial sync apply phase tries to fetch a remote document
Branch: master
https://github.com/mongodb/mongo/commit/129c1f22e71249e96f19717d315161f857e471ad

Comment by Githook User [ 14/Oct/16 ]

Author:

{u'username': u'judahschvimer', u'name': u'Judah Schvimer', u'email': u'judah@mongodb.com'}

Message: SERVER-26572 add stopTimestamp to DataReplicator stats
Branch: master
https://github.com/mongodb/mongo/commit/f3ab276dbbbc1a96d76d49373fa04e0a20f01cd6

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