![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Francis Upton
|
|
Components:
|
ec2-plugin |
|
Created:
|
05/Feb/15 6:10 AM
|
|
Description:
|
We heavily utilize this plugins with 4 separate models created in our master for different AMIs for different type of build project.
While the scale capability is great, we do encounter high frequency of out-of-sync slave. This means that we have Jenkins slave being marked offline, but the actual EC2 instance are still in "running" state instead of "stopped" state.
Not sure if it is something to do with AWS side unable to stop instance, but at least the Jenkins.log does not indicate that is the scenario.
Given the high volume and high frequency of this situation, we are actually bleeding money without added build capacity for those out-of-sync slave.
|
|
Environment:
|
Jenkins ver. 1.580.3
EC2 Plugin ver. 1.24
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Kevin Cheng
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[email protected].
For more options, visit
https://groups.google.com/d/optout.
