Cap the PubChem 503 backoff so a transient throttle can't stall a crawl - #78
Merged
Merged
Conversation
An over-aggressive 503 backoff (up to 30s/call) turned a brief PubChem throttle into a ~40-minute stall. Cap the retry backoff at 4s so a transient throttle costs a second or two, not a hang; the shared imports mean both the properties and the odor/threshold crawlers benefit. Signed-off-by: Austin L. <86896075+rvnminers-A-and-N@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
An over-aggressive 503 backoff (up to 30s/call) turned a brief PubChem throttle into a ~40-min stall on the odor+threshold crawl. Cap the retry backoff at 4s — a transient throttle now costs a second or two, not a hang. Both the properties and odor/threshold crawlers benefit (shared
_get).