[SERVER-44303] Make OplogApplier own OpQueueBatcher Created: 29/Oct/19  Updated: 29/Oct/23  Resolved: 31/Oct/19

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

Type: Task Priority: Major - P3
Reporter: Haley Connelly Assignee: Haley Connelly
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-43001 Separate OplogApplier and OpQueueBatc... Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 2019-11-04
Participants:

 Description   

Currently, OpQueueBatcher is initialized locally inside OplogApplierImpl::_run().

To better clarify the relationship between OplogApplier and OpQueueBatcher, OpQueueBatcher should be owned by OplogApplier.



 Comments   
Comment by Githook User [ 31/Oct/19 ]

Author:

{'name': 'Haley Connelly', 'username': 'haleyConnelly', 'email': 'haley.connelly@10gen.com'}

Message: SERVER-44303 Make OplogApplierImpl own OpQueueBatcher
Branch: master
https://github.com/mongodb/mongo/commit/89546eafa602bb66badc33e0a91fe2b080a79d3a

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