Long-lived containers
A long-lived container is one with a timeout of over ten minutes in its revision settings. For the maximum possible timeout value, see Limits.
Note
This feature is in the Preview stage. To get access, contact tech support or your account manager.
Forced termination of a long-lived container instance
In some cases, Serverless Containers may forcibly terminate a long-lived container instance processing a call before the timeout specified in the container revision settings is reached.
In such cases, the Docker image code will receive a notification about the upcoming forced termination of the container instance. Such a notification is sent to the container ten minutes before the actual forced termination.
Once the notification about the upcoming forced termination of the container instance is sent:
- The container instance has up to ten minutes to complete processing the current calls.
- The container instance will no longer be receiving new calls.
- The container instance will be forcibly stopped as soon as it completes processing all the current calls or after ten minutes, whichever comes first.
Warning
If there are less than ten minutes left before the timeout specified in the container revision settings expires, no notification about the forced termination of the container instance will be sent to the Docker image code.