Project

Profile

Help

Story #5880

closed

Add ability to be more aggressive in retrying downloads for intermittent networking issues

Added by jsherril@redhat.com about 5 years ago. Updated over 4 years ago.

Status:
CLOSED - DUPLICATE
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Katello
Sprint:
Quarter:

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

Is duplicate of Pulp - Story #5286: As a user, a Remote should provide an option that allows download errors, e.g. 404 errors to still allow creation of a RepositoryVersionCLOSED - DUPLICATE

Actions
Actions #1

Updated by jsherril@redhat.com about 5 years ago

  • Description updated (diff)
Actions #2

Updated by jsherril@redhat.com about 5 years ago

  • Description updated (diff)
Actions #3

Updated by fao89 about 5 years ago

  • Tracker changed from Issue to Story
  • % Done set to 0
Actions #4

Updated by daviddavis almost 5 years ago

  • Status changed from NEW to CLOSED - DUPLICATE
Actions #5

Updated by daviddavis almost 5 years ago

  • Is duplicate of Story #5286: As a user, a Remote should provide an option that allows download errors, e.g. 404 errors to still allow creation of a RepositoryVersion added
Actions #6

Updated by ggainey over 4 years ago

  • Tags Katello added
  • Tags deleted (Katello-P2)

Also available in: Atom PDF