Project

Profile

Help

Task #6624

Document how Pulp handles the ServerDisconnectedError and why

Added by ttereshc 3 months ago. Updated 3 days ago.

Status:
NEW
Priority:
Normal
Assignee:
-
Category:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
Yes
Tags:
Documentation, Katello
Sprint:

Description

A new FAQ page

Create a new FAQ page and have this be the first FAQ. This should be a top-level page on the left-side of the navigation.

Behavior to document

At open floor today we touched on how Pulp 3 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]

Reasoning why

Two issues would occur if Pulp had a broad retry behavior such as in the cases above:

  1. If the server says stop by hanging up Pulp should stop. Similarly if the network delivers TCP segments so slowly TCP times our.

  2. If pulp did continue an actual network error would become a very slow failure, tons of retries for each content unit slowly failing one by one over hours

What can users who want retry do?

Users can restart their sync tasks. Pulp saves all the content it did receive on the timed-out sync, so the next time it syncs it doesn't need to redownload what it already got. Therefore when users do retry they effectively resume whenever the network and server is ready for that.


Related issues

Related to RPM Support - Issue #6589: Issues synching large Redhat reposCLOSED - NOTABUG<a title="Actions" class="icon-only icon-actions js-contextmenu" href="#">Actions</a>

History

#1 Updated by ttereshc 3 months ago

  • Related to Issue #6589: Issues synching large Redhat repos added

#2 Updated by rchan 3 months ago

  • Sprint Candidate changed from No to Yes

#3 Updated by bmbouter 3 months ago

  • Description updated (diff)

#4 Updated by bmbouter 3 months ago

  • Description updated (diff)

#5 Updated by rchan 3 months ago

  • Sprint set to Sprint 73

#6 Updated by rchan 2 months ago

  • Sprint changed from Sprint 73 to Sprint 74

#7 Updated by rchan about 2 months ago

  • Sprint changed from Sprint 74 to Sprint 75

#8 Updated by rchan about 1 month ago

  • Sprint changed from Sprint 75 to Sprint 76

#9 Updated by rchan about 1 month ago

  • Sprint changed from Sprint 76 to Sprint 77

#10 Updated by rchan 13 days ago

  • Sprint changed from Sprint 77 to Sprint 78

#11 Updated by daviddavis 3 days ago

  • Tags Katello added

#12 Updated by daviddavis 3 days ago

Removing per sprint planning

#13 Updated by rchan 3 days ago

  • Sprint deleted (Sprint 78)

Please register to edit this issue

Also available in: Atom PDF