archive/pillar
0
0
Fork 0
Code Issues 42 Pull Requests Projects Releases Wiki Activity

Retry GCS on 503 errors #49982

New Issue
Open
opened 2016-11-10 09:01:44 +01:00 by Sybren A. Stüvel · 2 comments
Sybren A. Stüvel commented 2016-11-10 09:01:44 +01:00
Copy Link

Google Cloud Service sometimes throws 503 Service Temporarily Unavailable errors at us. We might want to retry once or twice after such a reply, to see if the service has come up. However, we should consider this carefully, given that:

  • we probably want to pause for a second or two between retries, to give GCS to come up and service us again, and
  • during this delay the Pillar process is sleeping, blocking others from performing requests on it.

If we do this the wrong way, a hickup at GCS could cause all Pillar processes to hang in a retry loop, DOSsing ourselves.

Probably related to #48956.

Google Cloud Service sometimes throws 503 Service Temporarily Unavailable errors at us. We might want to retry once or twice after such a reply, to see if the service has come up. However, we should consider this carefully, given that: - we probably want to pause for a second or two between retries, to give GCS to come up and service us again, and - during this delay the Pillar process is sleeping, blocking others from performing requests on it. If we do this the wrong way, a hickup at GCS could cause all Pillar processes to hang in a retry loop, DOSsing ourselves. Probably related to #48956.
Sybren A. Stüvel commented 2016-11-10 09:01:44 +01:00
Author
Copy Link

Changed status to: 'Open'

Changed status to: 'Open'
Sybren A. Stüvel commented 2016-11-10 09:01:44 +01:00
Author
Copy Link

Added subscribers: @dr.sybren, @fsiddi, @pablovazquez

Added subscribers: @dr.sybren, @fsiddi, @pablovazquez
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Priority::High
Priority::Low
Priority::Normal
Status::Archived
Status::Confirmed
Status::Resolved
Type::Bug
Type::Design
Type::Patch
Type::Report
Type::To Do
legacy project
Infrastructure: Websites
legacy project
Pillar
legacy project
Pillar Framework
legacy project
Pillar Website
No Label
Priority::Normal
Status::Confirmed
Type::Design
legacy project
Pillar
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
blender-admin
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: archive/pillar#49982
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?