[SERVER-31654] ReplBatcher should recalculate batch limits after oplog is resized via replSetResizeOplog Created: 20/Oct/17  Updated: 06/Dec/22

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

Type: Improvement Priority: Major - P3
Reporter: Benety Goh Assignee: Backlog - Replication Team
Resolution: Unresolved Votes: 0
Labels: neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-31587 ReplBatcher has a long-running Operat... Closed
is related to SERVER-22766 Dynamic oplog sizing for WiredTiger n... Closed
Assigned Teams:
Replication
Participants:

 Description   

We added support for dynamically resizing the oplog on WiredTiger nodes using the replSetResizeOplog command in SERVER-22766. The ReplBatcher thread calculates the batch limit once based on the oplog size known at the time the thread is spawned. We should look at re-evaluating this batch limit whenever the oplog is resized.

This came out of a code review on SERVER-31587


Generated at Thu Feb 08 04:27:45 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.