Skip to content
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

Shorter timeouts of api requests #17

Open
bjoerge opened this issue Aug 16, 2012 · 2 comments
Open

Shorter timeouts of api requests #17

bjoerge opened this issue Aug 16, 2012 · 2 comments

Comments

@bjoerge
Copy link
Member

bjoerge commented Aug 16, 2012

HTTP calls to external services should have shorter timeouts. It looks the default timeout is < 60 seconds, which makes the app hang until it eventually gets killed by the master unicorn process.

A solution will be to set the timeout to ~ 10-30 seconds and raise an error to be logged.

@kytrinyx
Copy link
Contributor

The only pebble that I could see taking a significant amount of time at the moment is tiramisu. As far as I can tell, any other pebble that takes as much as 10 seconds to respond is probably in distress.

Could we have a default at 10 seconds (or something) and override this for tiramisu? Does tiramisu even use pebblebed?

@bjoerge
Copy link
Member Author

bjoerge commented Aug 16, 2012

Yeah, an overridable 10s should be sufficient in most cases I guess.

Don't think Tiramisu use pebblebed to communicate with other pebbles (it only talks to S3, afaik). But other services/apps using Tiramisu may benefit from a longer timeout. I.e. when uploading, depending on the size of the file, the request may (in rare cases) take a a little longer than 10 seconds. This also depends on the connection to S3.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants