Story #5880
closed
Add ability to be more aggressive in retrying downloads for intermittent networking issues
0%
Description
Currently pulp3 will abort a sync immediately if any download fails other than an HTTP response that has a status code of 429, 502, 503, or 504
I think there are situations where users may experience an intermittent issue with their networking or dns that causes the download to fail without actually getting to the remote server at all. This could be an aborted connection or a dns resolution failure. Ideally there would be some option that would allow pulp to retry those failures.
I fear that without this option a user syncing a large RPM repository may have a hard time ever completing the download if they don't have a perfect network (which you'd hope all networks were).
So my proposal would be that if this option was enabled, any error on download would be retried if:
1. it was an HTTP response of 429, 502, 503, or 504
2. No http response was received (lower level error)
Related issues
.