[SERVER-38922] Correctly account for applyOps in oplog application batch size counting Created: 10/Jan/19  Updated: 05/Dec/22  Resolved: 14/Nov/22

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

Type: Task Priority: Major - P3
Reporter: Judah Schvimer Assignee: Backlog - Replication Team
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Assigned Teams:
Replication
Participants:

 Description   

applyOps commands are mixed in with other CRUD ops in oplog application batches, but we only count them as 1 operation towards the maximum allowed batch size. We should instead count them as the number of operations in the applyOps since that is a more realistic estimate of the amount of cache required for applying them.



 Comments   
Comment by Connie Chen [ 09/Nov/22 ]

Throwing this back into "needs scheduling" to be re-triaged as we are closing PM-1725 as won't do since it has been superseded by PM-3007

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