[SERVER-39618] Investigate and implement optimal minimum number of tickets to be assigned by ticket admission mechanism Created: 15/Feb/19  Updated: 27/Oct/23  Resolved: 28/May/19

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

Type: Task Priority: Major - P3
Reporter: Maria van Keulen Assignee: Maria van Keulen
Resolution: Works as Designed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-39868 Avoid throttling replica set elections Closed
Related
Sprint: Execution Team 2019-06-03
Participants:

 Description   

The ticket admission flow control algorithm currently uses 100 tickets as its minimum number to allocate in any given period, regardless of the number calculated to control lag. This handling is to allow system operations that take a global IX lock a legitimate opportunity to be processed, but is still arbitrary. Investigation should be done to determine what the ideal minimum value is.



 Comments   
Comment by Brian Lane [ 21/May/19 ]

greg.mckeon I only see this one and 41241 in the current sprint. I'll defer to Maria, and I wouldn't hold up rc0 for this. So with that thought, it could be 4.2.0. The change here is easy, its the work to decide if we need to change the ticket number that isn't as trivial.

Cheers!

-Brian

Generated at Thu Feb 08 04:52:35 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.