Details
-
Bug
-
Resolution: Duplicate
-
Medium
-
None
-
2.6, 2.6.1
-
None
Description
Elastic instances are not automatically shut down according to the instance management configuration
Shutting down instances takes app 45 min even though 10 min is defined below.
un 17, 2010 9:47:25 PM Requested that new elastic instance be created for configuration: Default Jun 17, 2010 9:47:27 PM Elastic instance i-3e786655 transitioned from STARTING to IDENTIFIED. Jun 17, 2010 9:49:22 PM Elastic instance i-3e786655 transitioned from IDENTIFIED to RUNNING. Jun 17, 2010 9:49:47 PM An elastic instance is loading on instance: i-3e786655 Jun 17, 2010 9:51:19 PM Elastic Agent "Elastic Agent on i-3e786655" started on instance i-3e786655 Jun 17, 2010 9:51:25 PM Requested that new elastic instance be created for configuration: Default Jun 17, 2010 9:51:25 PM Requested that new elastic instance be created for configuration: Default Jun 17, 2010 9:51:28 PM Elastic instance i-2c796747 transitioned from STARTING to IDENTIFIED. Jun 17, 2010 9:51:28 PM Elastic instance i-22796749 transitioned from STARTING to IDENTIFIED. Jun 17, 2010 9:53:24 PM Elastic instance i-2c796747 transitioned from IDENTIFIED to RUNNING. Jun 17, 2010 9:53:25 PM Elastic instance i-22796749 transitioned from IDENTIFIED to RUNNING. Jun 17, 2010 9:53:48 PM An elastic instance is loading on instance: i-2c796747 Jun 17, 2010 9:53:51 PM An elastic instance is loading on instance: i-22796749 Jun 17, 2010 9:55:37 PM Elastic Agent "Elastic Agent on i-22796749" started on instance i-22796749 Jun 17, 2010 9:55:41 PM Elastic Agent "Elastic Agent on i-2c796747" started on instance i-2c796747 Jun 17, 2010 10:41:25 PM Elastic Agent "Elastic Agent on i-3e786655" stopped on instance i-3e786655 Jun 17, 2010 10:41:25 PM Elastic instance i-3e786655 transitioned from RUNNING to SHUTTING_DOWN. Jun 17, 2010 10:41:25 PM Requested termination of elastic instance: i-3e786655 Jun 17, 2010 10:41:43 PM Elastic instance i-3e786655 transitioned from SHUTTING_DOWN to TERMINATED. Jun 17, 2010 10:41:43 PM Detected that the elastic instance i-3e786655 has stopped. Jun 17, 2010 10:46:25 PM Elastic Agent "Elastic Agent on i-22796749" stopped on instance i-22796749 Jun 17, 2010 10:46:25 PM Elastic instance i-22796749 transitioned from RUNNING to SHUTTING_DOWN. Jun 17, 2010 10:46:25 PM Requested termination of elastic instance: i-22796749 Jun 17, 2010 10:46:25 PM Elastic Agent "Elastic Agent on i-2c796747" stopped on instance i-2c796747 Jun 17, 2010 10:46:25 PM Requested termination of elastic instance: i-2c796747 Jun 17, 2010 10:46:26 PM Elastic instance i-2c796747 transitioned from RUNNING to SHUTTING_DOWN. Jun 17, 2010 10:46:44 PM Elastic instance i-2c796747 transitioned from SHUTTING_DOWN to TERMINATED. Jun 17, 2010 10:46:44 PM Detected that the elastic instance i-2c796747 has stopped. Jun 17, 2010 10:46:53 PM Elastic instance i-22796749 transitioned from SHUTTING_DOWN to TERMINATED. Jun 17, 2010 10:46:53 PM Detected that the elastic instance i-22796749 has stopped.
Configuration
Elastic Bamboo Global Settings
Maximum Number of Elastic Instances:
5
Automatic Shutdown:
EC2 instances will be automatically terminated 300 seconds after the agent process ends
Elastic Bamboo AWS Settings
AWS account identifier files are not automatically uploaded to new elastic instances.
Automatic Elastic Instance Management
Bamboo will automatically manage your elastic instances based on the following criteria:
- Bamboo will shut down elastic instances which have been idle for more than 10 minute(s).
- A maximum of 4 elastic instance(s) can be started each minute.
- New elastic instances will be started when all of the following conditions have been met:
o There are at least 2 build(s) in a queue.
o There are at least 1 build(s) in a queue that are executable on elastic images.
o The average time builds have been waiting in a queue is at least 2 minute(s).
