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.
Refactor async retries to use Shard::OwnerRetryStrategy
- Assignee:
-
Unassigned
- Reporter:
-
Guillaume Racicot
- Votes:
-
0 Vote for this issue - Watchers:
-
2 Start watching this issue
- Created:
- Updated:
- Resolved: