Details
-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
0
-
Description
Summary
If a time is set for Idle agent shutdown then all Elastic agents will use this setting including agents that have been manually started.
Environment
Bamboo 7.0.4
AWS EC2 instance
Elastic Agent
Steps to Reproduce
- Under https://<bamboo-url>/admin/elastic/editElasticConfig.action or Bamboo administration >> Overview >> Elastic Bamboo >> Configuration, hit Edit configuration
- In Automatic elastic instance management, select Custom under Elastic instance management
- Set up '10' for Idle agent shutdown delay
- In Miscellaneous, select Automatic termination
- Set up '10 for Shutdown delay
- Save the configuration
- # Under https://<bamboo-url>/admin/elastic/editElasticConfig.action or Bamboo administration >> Overview >> Elastic Instances >> Start New Elastic Instances
Desired Results
After 10 minute of being idle, any instance that has been started automatically by Bamboo should terminate in AWS. Elastic agents that were started manually should not follow the idle timeout.
Actual Results
All Elastic agents will timeout if Idle.
Custoer has a use case where they would like to start 2 Elastic agent that persist during business hours. Currently they need to script with cron to ensure that there are always two agents and restarting them if they have idled. The preference and this feature request it to have manually started agents not idle timeout or atleast have a separate configurable timeout.