-
Notifications
You must be signed in to change notification settings - Fork 4
Open
Labels
developmentStandard developmentStandard developmentr&d:polykey:core activity 4End to End Networking behind Consumer NAT DevicesEnd to End Networking behind Consumer NAT Devices
Description
Specification
So primarily the idea here is that one could do this for a few commands where it supports it. The
--retry-countwill retry something up to a limit, while--retry-intervalwill be the delay between retries.At the same time, one must define what it means to retry something. What exceptions are considered retryable... maybe it depends on the command itself. It's not exactly generic.
At any case if this is needed, this needs to rebased and redone due to big changes in PK.
Additional context
- CLI Retry Options due to Intermittent Network Polykey#325 - Never merged because of other priorities
- https://aws.amazon.com/builders-library/timeouts-retries-and-backoff-with-jitter/
- https://aws.amazon.com/blogs/architecture/exponential-backoff-and-jitter/
Tasks
- Put
--retry-count,--retry-interval,--retry-multiplierintosrc/utils/options.ts - Design the sentinel values for each
- Default to retrying 0 times,
1000ms interval and multiplier of1 - Consider the need for a
--retry-jitter? - requires review of AWS blogs
Metadata
Metadata
Assignees
Labels
developmentStandard developmentStandard developmentr&d:polykey:core activity 4End to End Networking behind Consumer NAT DevicesEnd to End Networking behind Consumer NAT Devices