[SERVER-10751] Keep fetching oplog during index creation of initial resync Created: 12/Sep/13  Updated: 06/Dec/22  Resolved: 08/Sep/16

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

Type: Improvement Priority: Major - P3
Reporter: Tuomas Silen Assignee: Backlog - Replication Team
Resolution: Duplicate Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-7200 use oplog as op buffer on secondaries Closed
Related
related to SERVER-14805 Use multithreaded oplog replay during... Closed
Assigned Teams:
Replication
Participants:

 Description   

When doing an initial resync for a secondary where large indexes are created it easily ends up to a "too stale" state as the primary's oplog is too small. When the index creation takes several days the oplog size would have to be enormous to handle it or you'd have to take another secondary down to copy the files over.

Why not just keep fetching the oplog during the index creation instead of trying to fetch them all after the indexes are created?



 Comments   
Comment by Eric Milkie [ 08/Sep/16 ]

This is now implemented via SERVER-7200.

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