[SERVER-50024] Make tunable server parameters for TenantOplogProcessing constants Created: 30/Jul/20  Updated: 29/Oct/23  Resolved: 02/Dec/20

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

Type: Bug Priority: Major - P3
Reporter: Matthew Russotto Assignee: Vishnu Kaushik
Resolution: Fixed Votes: 0
Labels: pm-1791_polish
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Repl 2020-11-30, Repl 2020-12-14
Participants:

 Description   

The constants

kTenantApplierBatchSizeBytes,
kTenantApplierBatchSizeOps,
kMinOplogEntriesPerThread,
kTenantApplierThreadCount

in the TenantOplogApplier should be server parameters instead of constants. Except kTenantApplierThreadCount, all should be settable at run time and take effect between batches.



 Comments   
Comment by Githook User [ 02/Dec/20 ]

Author:

{'name': 'Vishnu Kaushik', 'email': 'vishnu.kaushik@mongodb.com', 'username': 'kauboy26'}

Message: SERVER-50024 make tunable server parameters for TenantOplogProcessing constants
Branch: master
https://github.com/mongodb/mongo/commit/597c867f9adb8a74eaa18d3427a889c01f76aa22

Comment by Xuerui Fa [ 20/Nov/20 ]

matthew.russotto a few quick questions:

1. Should we retain the current values of each of these constants as the default?
2. For all the server params except kTenantApplierThreadCount, should we allow users to set at both startup and run time?

CC pavithra.vetriselvan

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