Refactor async retries to use Shard::OwnerRetryStrategy

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Workload Resilience
    • Fully Compatible
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Async code need to explicitly retain ownership of the retry strategy. In sync code we keep the variable on the stack, but future based code would need to explicitly keep instances of shards alive for the lifetime of the retry strategy. We should use the newly introduced Shard::OwnerRetryStrategy in those cases.

            Assignee:
            Unassigned
            Reporter:
            Guillaume Racicot
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: