[SERVER-86324] Limit max number of keys to check Created: 06/Feb/24  Updated: 07/Feb/24

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

Type: Task Priority: Major - P3
Reporter: Xuerui Fa Assignee: Backlog - Replication Team
Resolution: Unresolved Votes: 0
Labels: pm-855-milestone-5
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Replication
Participants:

 Description   

We should consider adding a server parameter as limit on the max number of keys to check in a batch on secondaries (independent of batch boundaries), both for extra keys and missing keys checks. This is because if there are many inconsistent entries but we use minKey as the start of the first batch, or maxKey as the end of the last batch, those first/final batches may do a lot of work on the secondaries that the primary may not expect. As a result, this can slow down oplog application.


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