Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Unresolved
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
- repl-shortlist

Assigned Teams:

Replication
Backwards Compatibility:
Fully Compatible
Confidence Status:
None
Work Order:
3
Size Category:
TBD
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

Right now the default number of applier threads is 16, but that does not scale as a machine has a larger number of cores (and therefore a higher ability to parallelize oplog application). We should change the default calculation of this field.

We should investigate whether the new default is safe across all instance sizes and post the results of that investigation on this ticket for posterity.

is related to

SERVER-34938 Secondary slowdown or hang due to content pinned in cache by single oplog batch

Closed

related to

SERVER-108822 Investigate whether repl batch size should be impacted by the number of oplog applier threads

Needs Scheduling

Assignee:: Unassigned
Reporter:: Samyukta Lanka
Participants:: Githook User, Mothra Jira Bot, Samyukta Lanka
Votes:: 0 Vote for this issue
Watchers:: 14 Start watching this issue

Created:: Jul 17 2025 07:21:04 PM UTC
Updated:: Aug 07 2025 08:59:56 PM UTC
Confidence Status Last Update:: 05/Aug/25 9:37 PM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates