[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: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 25 weeks, 2 days ago | ||||||||
| Story Points: | 1 | ||||||||
| Description |
| Comments |
| Comment by Corry Root [ 14/Aug/23 ] |
DESCRIPTIONI 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. STAGINGwiredTiger.concurrentTransactions wiredTigerConcurrentReadTransactions wiredTigerConcurrentWriteTransactions JIRADOCSP-10266 DOCSP-32209 BUILD LOG |
| 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. |