Relying on the infrastructure to police your algorithm’s implementation doesn’t make much sense.
If you’re doing some operation with a loop, you can simply add a check every few iterations and abort if it’s taking too long. Using timers might be an option, depending on the language you are using. But being explicit within the algorithm is probably a better engineering practice. > On Jan 31, 2020, at 3:40 AM, Patrice B <patrice.bertrand...@gmail.com> wrote: > > Thank you for your time. I do understand that task queues and cron jobs may > need a longer timeout value. > > My question really is this : is there no way to configure an instance in such > a way that HTTP requests are killed on timeout after say 10 minutes ? > > And if there is no way to achieve this, as seems to be the case, then how > would you suggest to protect an instance against a request that would keep > running forever ? Should be start a timer and attempt to handle timeout > manually ? > > > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to google-appengine+unsubscr...@googlegroups.com > <mailto:google-appengine+unsubscr...@googlegroups.com>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/google-appengine/cbc75d76-591f-4f58-bff3-42d6fe0b8b4c%40googlegroups.com > > <https://groups.google.com/d/msgid/google-appengine/cbc75d76-591f-4f58-bff3-42d6fe0b8b4c%40googlegroups.com?utm_medium=email&utm_source=footer>. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/DAC3FA17-71F1-43F1-94FB-99FF06F54B29%40gmail.com.
