[SERVER-3482] oplog replay should check first element in oplog before going backwards for initial sync performance Created: 26/Jul/11  Updated: 12/Jul/16  Resolved: 01/Aug/11

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

Type: Improvement Priority: Major - P3
Reporter: Eliot Horowitz (Inactive) Assignee: Aaron Staple
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Comments   
Comment by auto [ 31/Jul/11 ]

Author:

{u'login': u'astaple', u'name': u'Aaron', u'email': u'aaron@10gen.com'}

Message: SERVER-3482 update tests, handle empty oplog properly
Branch: master
https://github.com/mongodb/mongo/commit/26e10443f5a8530853756f00ffe4aae77e6f9cae

Comment by auto [ 31/Jul/11 ]

Author:

{u'login': u'astaple', u'name': u'Aaron', u'email': u'aaron@10gen.com'}

Message: SERVER-3482 check oldest op first when doing oplog replay, wassert instead of massert on encountering empty extent
Branch: master
https://github.com/mongodb/mongo/commit/175e0392475935552f83b1719936750e362f45cc

Comment by Eliot Horowitz (Inactive) [ 26/Jul/11 ]

Right.

So full process should be

1) check first element in capped collection
2) scan backwards for 5 secconds
3) extent by extent scan

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