[DOCS-16042] Investigate changes in SERVER-76012: Rename kNone option for storageEngineConcurrencyAdjustmentAlgorithm server parameter Created: 14/Apr/23  Updated: 13/Nov/23  Resolved: 15/Aug/23

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 7.0.0-rc0, 7.1.0-rc0, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Corry Root
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-76012 Rename kNone option for storageEngine... Closed
Participants:
Days since reply: 25 weeks, 2 days ago
Story Points: 1

 Description   
Original Downstream Change Summary

For execution control, we added a new server parameter called "storageEngineConcurrencyAdjustmentAlgorithm" that takes two options, "throughputProbing" and "fixedConcurrentTransactions". This might end up being for special use only (customers must go through support team) and will not require public documentation.

Description of Linked Ticket

kNone translates to an empty string, which is not informative at all to a user. We originally thought we would be removing this server parameter but decided to keep it for future flexibility in the execution control algorithm.



 Comments   
Comment by Corry Root [ 14/Aug/23 ]

gregory.noma@mongodb.com

DESCRIPTION

I added a release notes for the new execution control algorithm. I added an important note to the parameters that disable the algorithm. I added an important note to the serverStatus that indicates the ticket count.

STAGING

Release Notes

wiredTiger.concurrentTransactions

wiredTigerConcurrentReadTransactions

wiredTigerConcurrentWriteTransactions

JIRA

DOCSP-10266

DOCS-16042

DOCSP-32209

BUILD LOG

BUILD

Comment by Corry Root [ 14/Aug/23 ]

shameek.ray@mongodb.com and gregory.noma@mongodb.com confirmed that we shouldn't document these new parameters, but note for the existing parameters that they disable the dynamic algorithm.

Comment by Gregory Noma [ 28/Jul/23 ]

storageEngineConcurrencyAdjustmentAlgorithm is only settable at startup, and users can already disable the feature at startup by setting the wiredTigerConcurrentReadTransactions/storageEngineConcurrentReadTransactions or wiredTigerConcurrentWriteTransactions/storageEngineConcurrentWriteTransactions parameters, which are publicly documented. So also documenting storageEngineConcurrencyAdjustmentAlgorithm wouldn't really change anything in terms of allowing users to turn off the feature. shameek.ray@mongodb.com any thoughts here?

Comment by Kanchana Sekhar [ 27/Jul/23 ]

 pavithra.vetriselvan@mongodb.com mentioned that we probably shouldn't document these parameters as it’s a way for users to turn off a default 7.0 feature. These parameters were added as a failsafe that TSE’s could suggest if a customer needed to turn it off.

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