-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Retry failed external connections #98
Comments
I agree with this. We should probably do this when refactoring shed-tools #91 . The code is very spaghetti ish now. I volunteer, but it is unclear yet when I have time to do this. Probably somewhere in july august. |
I have been thinking about this. Wouldn't be a global BIOBLEND_RETRY environment variable or some other setting in bioblend preferable? I mean, it would be a lot more effective than fixing bioblend's errors in all the tools that use it. |
Yeah that could work @rhpvorderman. Something sort of like logging?
You have a good point that it'd be easier to fix there than everything that depends on it. @nsoranzo do you have an opinion on this? |
For GET requests it could be added to BioBlend, for POST probably not a good idea. Not sure about PUT and DELETE. |
obviously will default to 0 so we don't add a footgun for bioblend users.
|
For a start we can add a |
@rhpvorderman you can do some of this already via
|
@nsoranzo I'm working up a PR now. Would allowing the user to choose which methods to retry be desirable? |
I think users may not be too familiar with REST API concepts to make the best choice, depends if there is a use case. |
How about something like this? (Does not have to be this) galaxyproject/bioblend#266 Has I think my only case is things like installation, but there I guess we possibly need more complex/intelligent retry logic. |
We've been running our automated tool installation and we occasionally see errors due to transient network failures that cause failures of the jenkins job. If we wrapped all bioblend / external network connections in a retry (we use https://github.com/litl/backoff for some stuff here) this would be extremely helpful.
E.g.
The text was updated successfully, but these errors were encountered: