Do not require stepdown token to construct CancelState

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 9.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Cluster Scalability
    • Fully Compatible
    • ClusterScalability 27Apr-11May
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      We jump through a lot of hoops to cope with the fact that we do not have the stepdown token from the PrimaryOnlyService until run() is called, but we can potentially interact with our cancellation state before this. Some examples of functions that are needlessly complicated:

      We should modify CancelState such that it can be created without a stepdown token, and allow for attaching the stepdown token later. It should be able to handle abort signals prior to the stepdown token being attached. Callers that acquire tokens from the CancelState prior to the stepdown token being attached should be properly notified after the stepdown token is attached.

            Assignee:
            Brett Nawrocki
            Reporter:
            Brett Nawrocki
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: