[SERVER-68793] Investigate if AdmissionContext::_startProcessingTime is valid during resize Created: 12/Aug/22 Updated: 29/Oct/23 Resolved: 05/Sep/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.2.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Haley Connelly | Assignee: | Jordi Olivares Provencio |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Execution Team 2022-08-22, Execution Team 2022-09-05, Execution Team 2022-09-19 | ||||||||
| Participants: | |||||||||
| Description |
|
Prior to
Now, it is initialized as
We should check if initializing the TicketSource tick to 0 instead of its default {} means the _startProcessingTime computed for ticketHolders will spit unrealistic values when the ticketHolder is resized. Example: TicketHolderWithQueueingStats::resize() calls TicketHolderWithQueueingStats::_release() with an AdmissionContext defined on the stack that never has its _startProcessingTime initialized to a non-zero value before it is used to compute the _totalTimeProcessingMicros
|
| Comments |
| Comment by Githook User [ 05/Sep/22 ] |
|
Author: {'name': 'Jordi Olivares Provencio', 'email': 'jordi.olivares-provencio@mongodb.com', 'username': 'jordiolivares'}Message: |
| Comment by Haley Connelly [ 16/Aug/22 ] |
|
We should be testing the resize() method since there aren't existing tests for it. |