Skip to content
This repository was archived by the owner on May 6, 2020. It is now read-only.

fix(registry): retry pull/push/tag 3 times - should help with slow networks and slow registries#979

Merged
helgi merged 1 commit intodeis:masterfrom
helgi:retry_registry
Aug 15, 2016
Merged

fix(registry): retry pull/push/tag 3 times - should help with slow networks and slow registries#979
helgi merged 1 commit intodeis:masterfrom
helgi:retry_registry

Conversation

@helgi
Copy link
Copy Markdown
Contributor

@helgi helgi commented Aug 12, 2016

Fixes #977

@helgi helgi added this to the v2.4 milestone Aug 12, 2016
@helgi helgi self-assigned this Aug 12, 2016
@deis-bot
Copy link
Copy Markdown

@mboersma and @krancour are potential reviewers of this pull request based on my analysis of git blame information. Thanks @helgi!

@codecov-io
Copy link
Copy Markdown

codecov-io commented Aug 15, 2016

Current coverage is 85.18% (diff: 100%)

No coverage report found for master at 4273f76.

Powered by Codecov. Last update 4273f76...4412ab5

@slack
Copy link
Copy Markdown
Member

slack commented Aug 15, 2016

SGTM, does this get logged anywhere that an operator would see?

@helgi
Copy link
Copy Markdown
Contributor Author

helgi commented Aug 15, 2016

No, I opted not to do that, tho if it fails 3 times then it will raise the errors all the way up

@helgi helgi merged commit bf82529 into deis:master Aug 15, 2016
@helgi helgi deleted the retry_registry branch August 15, 2016 23:32
@felixbuenemann
Copy link
Copy Markdown
Contributor

@helgi Do you think your fix will also help with errors like this:

Successfully built a6b761447898
Pushing to registry
remote: etail":{"message":"Put http://localhost:5555/v1/repositories/cms/: EOF"},"error":"Put http://localhost:5555/v1/repositories/cms/: EOF"}

I'm using an S3-backed on-cluster registry where the bucket is in the same region as the nodes.

@helgi
Copy link
Copy Markdown
Contributor Author

helgi commented Aug 18, 2016

It could potentially help, only if the network starts behaving or resuming works, if part of the data got pushed.

Are you seeing that consistently or sporadically?

@felixbuenemann
Copy link
Copy Markdown
Contributor

Sporadically, I forgot to check all the logs to get a better insight into what went wrong.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants