This article describes the behavior of the EC2 instances launched by Domino for use as executors.
When a run or workspace is launched, it is scheduled to run on a specific EC2 instance. This could mean launching a new EC2 instance of the target hardware tier, or starting one that has been stopped. EC2 instances that are stopped are put to sleep, but are not terminated.
Once an executor becomes idle, it will be subject to lifecycle management by the Domino application:
If no runs have been scheduled on a machine for 120 minutes, it will be stopped. This time period is controlled by the executorStopTimeout configuration point. When the instance is stopped, the only AWS costs it will generate are for the EBS volumes attached to it. You can view how long an instance has been idle or stopped under the Instance State column on the Dispatcher page. In the example below, prod-exec-d-free-107 has been in the stopped state for approximately 13 hours. Dispatcher">-_Domino.png
While in the stopped state, an executor can be woken up for a run if it is needed. This is preferred over immediately terminating the executor as it is more efficient for the machine to go from Stopped to Running than to launch a new one.
After the executorTerminateTimeout has passed, the executor will be terminated. The default for this is 3 days. Once terminated, the machine no longer exists, and there are no longer charges to AWS.