[SERVER-73716] Compatibility between concurrency adjustment task and user-defined concurrency levels Created: 07/Feb/23  Updated: 27/Oct/23  Resolved: 28/Mar/23

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

Type: Task Priority: Major - P3
Reporter: Gregory Noma Assignee: Gregory Noma
Resolution: Gone away Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-73460 Ticket adjustment algorithm based on ... Closed
Sprint: Execution Team 2023-04-03
Participants:

 Description   

A user can specify custom concurrency levels via the storageEngineConcurrentWriteTransactions and storageEngineConcurrentReadTransactions server parameters. We should make sure the interactions between these parameters and any concurrency adjustment algorithm make sense. For instance, currently the throughput probing algorithm requires both the read and write concurrency levels to be equal, so we shouldn't allow it to be specified if the concurrency level parameters are not equal. Additionally, we should consider how to handle a user attempting to set these parameters at runtime if dynamic concurrency adjustment is running.


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