[SERVER-76598] Execution control uses wrong value to probe down Created: 27/Apr/23  Updated: 29/Oct/23  Resolved: 28/Apr/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.1.0-rc0, 7.0.0-rc1

Type: Bug Priority: Major - P3
Reporter: Louis Williams Assignee: Louis Williams
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Problem/Incident
Related
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v7.0
Sprint: Execution Team 2023-05-01
Participants:
Linked BF Score: 135

 Description   

When deciding whether or not to probe for fewer tickets, we look at the instantaneous number of tickets, rather than the peak in the last period.

Additionally, when choosing to probe down, we should be using the _stableConcurrency, not peakUsed.



 Comments   
Comment by Githook User [ 28/Apr/23 ]

Author:

{'name': 'Louis Williams', 'email': 'louis.williams@mongodb.com', 'username': 'louiswilliams'}

Message: SERVER-76598 Throughput probing down should look at peak used
Branch: v7.0
https://github.com/mongodb/mongo/commit/1b7cac9dffb0be64ce39daaf6e7708a0265d2538

Comment by Githook User [ 28/Apr/23 ]

Author:

{'name': 'Louis Williams', 'email': 'louis.williams@mongodb.com', 'username': 'louiswilliams'}

Message: SERVER-76598 Throughput probing down should look at peak used
Branch: master
https://github.com/mongodb/mongo/commit/b6d7f0ecef2dad16f6d15b51e0f21a6f99579db1

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