Track absolute napTime in DeferredToken

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major - P3
    • 9.0.0-rc0, 7.0.41
    • Affects Version/s: None
    • Component/s: None
    • None
    • Workload Resilience
    • Fully Compatible
    • v7.0
    • 200
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The system can wait arbitrarily long between acquiring a DeferredToken (token acquisition resulted in queuing) and calling get() on it. This leads to subtle inaccuracy in the production queuing implementation, but also non-determinism in test. Instead, we should track the absolute deadline for the deferred token's "nap time" using the current tick source.

            Assignee:
            Matt Broadstone
            Reporter:
            Matt Broadstone
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: