Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Pending code changes (auto-populated)
View issue level access limits(Press Alt + Right arrow for more information)
Request for new functionality
View staffing
Description
What you would like to accomplish:
Allow for GAE Flex endpoints to enjoy the same 24 hour timeout as GAE Standard under manual/basic scaling.
We use App Engine as the target for Cloud Tasks to run some long-running background tasks on App Engine service in both staging and production GCP projects.
Currently for GAE Flex endpoints, long-running requests are timed out at 60 minutes [1] and return a
504past that deadline, causing Cloud Tasks to retry the requests. For most of the requests, a 1-hour limit is reasonable, but in some instances it is very problematic to retry the whole request after it has already been running for an hour.Additionally, we cannot move these tasks to GAE Standard (which would benefit from the much-extended 24 hours deadline) since our long-running tasks require more memory and disk space than we could get with Standard, which offers a max RAM allocation at 2048 MB -- we are currently running with 16GB RAM and 50GB storage on Flex.
[1]https://cloud.google.com/tasks/docs/creating-appengine-handlers#timeouts