Skip to content

Add retry backoff max and jitter settings [RHELDST-32465] #35

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
crungehottman merged 1 commit into from
Jul 22, 2025
+5 −0
Merged

Add retry backoff max and jitter settings [RHELDST-32465] #35

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions fastpurge/_client.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -106,6 +106,9 @@ class FastPurgeClient(object):
MAX_RETRIES = int(os.environ.get("FAST_PURGE_MAX_RETRIES", "10"))

RETRY_BACKOFF = float(os.environ.get("FAST_PURGE_RETRY_BACKOFF", "0.15"))
RETRY_BACKOFF_MAX = float(os.environ.get("FAST_PURGE_RETRY_BACKOFF_MAX", "150"))
RETRY_BACKOFF_JITTER = float(os.environ.get("FAST_PURGE_RETRY_JITTER", "2"))

# Default purge type.
# Akamai recommend "invalidate", so why is "delete" our default?
# Here's what Akamai docs have to say:
Expand Down Expand Up @@ -235,6 +238,8 @@ def __retry_policy(self):
retries = LoggingRetry(
total=self.MAX_RETRIES,
backoff_factor=self.RETRY_BACKOFF,
backoff_max=self.RETRY_BACKOFF_MAX,
backoff_jitter=self.RETRY_BACKOFF_JITTER,
# We strictly require 201 here since that's how the server
# tells us we queued something async, as expected
status_forcelist=[status.value for status in HTTPStatus
Expand Down