[Pulp-dev] No-Retry Behaviour on Network Errors: call for feedback and concerns

Brian Bouterse bmbouter at redhat.com
Tue May 12 20:41:44 UTC 2020

tl;dr: pulp does not retry when there are network errors or the server
hangs up. We are going to document this as part of this issue
https://pulp.plan.io/issues/6624 Please share concerns or feedback with
this plan before open floor on May 15th.

# Background

At open floor today we touched on how Pulp 3 downloading does not have
retry logic in these cases:
* the server hanging up the TCP connection
* network errors which cause TCP hangups
* http errors other than [429, 502, 503, 504]

# The Documentation Plan

The current plan is to document this onto docs.pulpproject.org as part of
this ticket https://pulp.plan.io/issues/6624. It will document:
* the no-retry behavior cases
* with the reasons why Pulp does not retry
* that users can retry and Pulp will effectively resume due to not having
to redownload content it already downloaded

# Feedback

Do you have concerns or other feedback with this plan? Is this the best
thing Pulp can do? If you are interested in sharing, please do before open
floor on Friday May 15th.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-dev/attachments/20200512/bee9bd2c/attachment.htm>

More information about the Pulp-dev mailing list