[SERVER-14805] Use multithreaded oplog replay during initial sync Created: 06/Aug/14  Updated: 25/Jun/15  Resolved: 05/Sep/14

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 2.6.3
Fix Version/s: 2.6.5, 2.7.7

Type: Improvement Priority: Major - P3
Reporter: Alexander Komyagin Assignee: Scott Hernandez (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
related to SERVER-7527 Improve speed of replication when in ... Closed
is related to SERVER-10751 Keep fetching oplog during index crea... Closed
Tested
Backwards Compatibility: Fully Compatible
Backport Completed:
Participants:

 Description   

Before 2.6.3 initial sync application is single-threaded, while our regular oplog replication is multi-threaded. This improvement request is for initial sync to work that same way.

It may (significantly) speed up the initial sync process for deployments with multiple active collections or databases to change the oplog application process.



 Comments   
Comment by Githook User [ 05/Sep/14 ]

Author:

{u'username': u'scotthernandez', u'name': u'Scott Hernandez', u'email': u'scotthernandez@gmail.com'}

Message: SERVER-14805: fix fassert numbers
Branch: v2.6
https://github.com/mongodb/mongo/commit/94411d9551465cd215e20960f99825d0a34e0ea8

Comment by Githook User [ 05/Sep/14 ]

Author:

{u'username': u'scotthernandez', u'name': u'Scott Hernandez', u'email': u'scotthernandez@gmail.com'}

Message: SERVER-14805: initialsync multithreaded oplog apply
Branch: master
https://github.com/mongodb/mongo/commit/823486e53a8160d20de06403228bb2c71fb127e1

Comment by Githook User [ 04/Sep/14 ]

Author:

{u'username': u'scotthernandez', u'name': u'Scott Hernandez', u'email': u'scotthernandez@gmail.com'}

Message: SERVER-14805: initialsync multithreaded oplog apply
Branch: v2.6
https://github.com/mongodb/mongo/commit/dbf18450b53d4ee1df99c701120567219608adc0

Comment by Eric Milkie [ 04/Sep/14 ]

Plan is to commit directly into 2.6 and then forward port.
Commit to 2.6 is approved, pending clean MCI patch run.

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