[SERVER-45574] Replace OplogFetcher with NewOplogFetcher Created: 14/Jan/20  Updated: 29/Oct/23  Resolved: 19/Feb/20

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

Type: Task Priority: Major - P3
Reporter: Samyukta Lanka Assignee: Lingzhi Deng
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-45714 Create a JSTest for repl.network.oplo... Closed
Gantt Dependency
has to be done after SERVER-45856 Make authenticating the connection in... Closed
Problem/Incident
Related
is related to SERVER-46257 OplogFetcher should run LogicalTimeMe... Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 2020-02-24
Participants:
Linked BF Score: 0

 Description   

This will involve using NewOplogFetcher in both initial sync and bgsync, as well as deleting the old OplogFetcher, AbstractOplogFetcher and all their unit tests.



 Comments   
Comment by Githook User [ 19/Feb/20 ]

Author:

{'username': 'ldennis', 'name': 'Lingzhi Deng', 'email': 'lingzhi.deng@mongodb.com'}

Message: SERVER-45574: Replace OplogFetcher with NewOplogFetcher

Comment by Githook User [ 19/Feb/20 ]

Author:

{'username': 'ldennis', 'name': 'Lingzhi Deng', 'email': 'lingzhi.deng@mongodb.com'}

Message: SERVER-45574: Use NewOplogFetcher in steady state replication and initial sync
Branch: master
https://github.com/mongodb/mongo/commit/06a03bc6ec3235c4ab79f7bd4e55083e3165a48b

Generated at Thu Feb 08 05:09:10 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.