Since using the Windows EC2 instances, I've noticed that instances would fail to start. I believe the root cause of the problem is related to EC2, however, Bamboo can be
improved to handle this situation more gracefully, as it will result in customers paying for EC2 costs that they don't use
Symptoms:
- Elastic instance has been started for a long period of time, yet the elastic agent is still in the pending state
- You are unable to remote desktop into the instance
- Running System Log in the EC2 console results in a non-response
Recommendation: Shutdown the elastic instance if the agent is stuck in the PENDING state for a long period of time (15 minutes?)
[BAM-9154] Handle Elastic Agents that hang in "Pending" state
Workflow | Original: JAC Suggestion Workflow [ 3015991 ] | New: JAC Suggestion Workflow 3 [ 3602105 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: Confluence Workflow - Public Facing v4 [ 2702683 ] | New: JAC Suggestion Workflow [ 3015991 ] |
Backlog Order (Obsolete) | Original: 30670000000 | |
Issue Type | Original: Improvement [ 4 ] | New: Suggestion [ 10000 ] |
Workflow | Original: Bamboo Workflow 2016 v1 [ 1413017 ] | New: Confluence Workflow - Public Facing v4 [ 2702683 ] |
Workflow | Original: Bamboo Workflow 2014 v2 [ 613702 ] | New: Bamboo Workflow 2016 v1 [ 1413017 ] |
Workflow | Original: Bamboo Workflow 2014 [ 598726 ] | New: Bamboo Workflow 2014 v2 [ 613702 ] |
Workflow | Original: Bamboo Workflow 2010 [ 304817 ] | New: Bamboo Workflow 2014 [ 598726 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: To be reviewed [ 10026 ] | New: Resolved [ 5 ] |
Status | Original: In Progress [ 3 ] | New: To be reviewed [ 10026 ] |
Fix Version/s | New: 3.2 final [ 19093 ] | |
Fix Version/s | Original: 3.2 RC1 [ 18890 ] |