[SERVER-43755] Throttle Cursor should not invariant when the current time is smaller than the last obtained time Created: 02/Oct/19 Updated: 29/Oct/23 Resolved: 02/Oct/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Gregory Wlodarek | Assignee: | Gregory Wlodarek |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Sprint: | Execution Team 2019-10-07 | ||||||||
| Participants: | |||||||||
| Description |
|
We should remove this invariant as the call above to get the currentMillis can go backwards in time, causing us to hit the invariant. We resolved a similar issue in In my workload where I use the ThrottleCursor I witness that once ~3 minutes the invariant failing because _startMillis is one higher than currentMillis and we only set _startMillis from currentMillis. |
| Comments |
| Comment by Githook User [ 02/Oct/19 ] |
|
Author: {'name': 'Gregory Wlodarek', 'username': 'GWlodarek', 'email': 'gregory.wlodarek@mongodb.com'}Message: |