Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-43755

Throttle Cursor should not invariant when the current time is smaller than the last obtained time

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.3.1
    • Affects Version/s: None
    • Component/s: Storage
    • Labels:
      None
    • Fully Compatible
    • ALL
    • Execution Team 2019-10-07

      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 SERVER-42991 for the ThrottleCursor unit tests.

      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.

            Assignee:
            gregory.wlodarek@mongodb.com Gregory Wlodarek
            Reporter:
            gregory.wlodarek@mongodb.com Gregory Wlodarek
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: