Increase of functions timeout
in progress
B
Bastian Vennemann
Timeout is set to 60 seconds. This value is a fixed setting and is too low for extensive ingestion functions.
For comparison: AWS Lambda functions timeout is set to 900 seconds (15 minutes).
A default value of 600 seconds would be helpful.
Even better would be the ability to set an individual timeout value per stitch application in the settings.
Drew DiPalma
Hi Folks!
As part of our upcoming re-brand of "Stitch" to "Realm" we'll also be migrating our feedback forum and joining the rest of MongoDB at feedback.mongodb.com, as part of that transition, we'll be shutting down this forum. We're still keeping track of this feedback and all of the related comments/discussions, but all future updates will be made here:
https://feedback.mongodb.com/forums/923521-realm/suggestions/40550602-increase-of-functions-timeout
Suneet Kumar
Hi Drew DiPalma,
Recently I found that most of my stitch-functions are failing because of the timeouts. Earlier, the same functions were able to run successfully within 30-40s but now timeout.
So, if possible, kindly either increase the performance of the system to have consistent runtime or increase the timeout.
Also, move it to high priority than other features, there is no point of adding new features if we can't utilize them.
Suneet Kumar
Just for the reference, average time to run the same logic of the function on my laptop is ~300 - 400ms but timeout in stitch :|
B
Bastian Vennemann
Hi Drew DiPalma,
Any news here?
I would really love to be able to configure a custom timeout value per stitch app.
M
Marc Blaesche
Hi Drew DiPalma,
increasing the timout can have other nice side effects. As an example:
Stitch apps do not have constant runtimes. Meaning the same code executed twice can have a runtime of 30 seconds and then the next time aroung 80 seconds.
As there is such great variability in the available performance from stitch regardless of the cluster size you are running (M10, M30, etc) and as a result different runtimes, an increase of the timeout would make apps crash less often.
Using stitch with these factors if uncertenty really makes it hard to stick with it as Jaco Olwagen already points out
Jaco Olwagen
Drew DiPalma Hi Drew, what is the timeout now? When will you increase it again?
Drew DiPalma
Jaco Olwagen: Hi Jaco – The timeout is still currently 90 seconds, can you give me an overview of your case and what your ideal timeout would be?
Jaco Olwagen
Drew DiPalma: Hi Drew, at the moment we would be happy with 180 seconds. We have created Stich API's for our clients to access their data once or twice daily. With a timeout of 90s this is not practical and we will have to look for another solution.
Jaco Olwagen
Hi, what is the limit now? Can you increase it some more?
Drew DiPalma
in progress
Hi Folks – Stitch's Function timeout has now been raised to 90s. We will continually monitor how this is effecting Stitch behavior and consider additional extensions to timeout. I will consider this ticket complete if/when Stitch Function timeout >=600s.
Jaco Olwagen
Please prioritize this, the 60s limit is forcing us to use other options