Coalesce all retry mechanisms in CS owned code

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Cluster Scalability
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      We have `primary_only_service_helpers::WithAutomaticRetry`, `resharding::WithAutomaticRetry`,`primary_only_service_helpers::RetryingCancelableOperationContextFactory`, and `resharding::RetryingCancelableOperationContextFactory` as options to choose from.

      When choosing an automatic retry mechanism, we should make the decision of what to choose from more obvious and keep the use consistent in the code. For example some places we use RetryingCancelableOperationContextFactory and nested code within this retry may use WithAutomaticRetry. 

      We should decide on the idiomatic way we want to do retries and only use that.

            Assignee:
            Unassigned
            Reporter:
            Ben Gawel
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: