You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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?
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.
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.
The text was updated successfully, but these errors were encountered: