Remove the use of atomics for AdmissionContext members

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Workload Resilience
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      All members of AdmissionContext are currently wrapped in atomics when, in fact, the members are operation-local and can be protected with the client lock. Helpfully, we already accept an OperationContext most places where we write these values (e.g. ScopedAdmissionPriority) so it should be fairly simple to remove the atomics and introduce client locking.

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

              Created:
              Updated: