You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Francois Gaudreault (JIRA)" <ji...@apache.org> on 2013/07/04 19:43:48 UTC
[jira] [Comment Edited] (CLOUDSTACK-3366) Autoscaling won't scale
down
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13700250#comment-13700250 ]
Francois Gaudreault edited comment on CLOUDSTACK-3366 at 7/4/13 5:43 PM:
-------------------------------------------------------------------------
Complement of information:
- We are using NS 10.1 build 112.15
- The ns.log returns :
Jul 4 17:42:34 <local0.warn> ns AutoScaleDaemon[1175]: Job with job type (1) for Service Group (Cloudf84eaf4ed3fe43aebbc4d2ff9f7311bc) -> Error : provserver_err_novmsfordeprovision
was (Author: fgaudreault):
Complement of information:
- We are using NS 10.1 build 112.15
- The ns.log returns :
Jul 4 17:42:34 <local0.warn> ns AutoScaleDaemon[1175]: Job with job type (1) for Service Group (Cloud241781113fa541a8aafb46bb45b8a719) -> Error : provserver_err_novmsfordeprovision
> Autoscaling won't scale down
> ----------------------------
>
> Key: CLOUDSTACK-3366
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3366
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Management Server
> Affects Versions: 4.1.0
> Reporter: Francois Gaudreault
> Priority: Critical
>
> When configuring Autoscaling, the autoscale will go UP, but not DOWN when traffic is back under thresholds.
> NetScaler seems to be triggering the SCALE_DOWN, but nothing happens on the CS side.
> Netscaler did:
> Autoscale: Evaluating autoscale policy Cloud-AutoScale-Policy-xxxxx-80-12Autoscale: Triggering autoscale action: SCALE_DOWN for policy: Cloud-AutoScale-ScaleDownAction-xxxxx-80Autoscale: :::925###POST /provision HTTP/1.1
> Host: NS
> Content-Length: 866
> { "autoscale" : { "ns" : { "sysid" : "98310000cb254307ee78" }, "vserver" : { "name" : "Cloud-VirtualServer-xxxxx-80", "servicegroupname" : "Cloudf84eaf4ed3fe43aebbc4d2ff9f7311bc" }, "cloudprofile" : { "type" : "CLOUDSTACK", "url" : "http://172.30.100.15:8080/client/api", "apiKey" : "x2134OIL1TKNyW6PahIq4NubxMn1tK3krpQFyDWks8fv_[...]", "sharedsecret" : "HtpqjvHENGMqZLBcn_o-_[...]" }, "action" : { "type" : "SCALE_DOWN", "params" : "command=destroyVirtualMachine&lbruleid=24aab38f-f466-45c5-9878-484841ba1b9d", "quiettime" : "300", "destroyVMGracePeriod" : "30" }, "autoprovisiondns" : { "nsdomainname" : "autoscale-internal_server_Cloudf84eaf4ed3fe43aebbc4d2ff9f7311bc", "nsservername" : "autoscale-internal_server_Cloudf84eaf4ed3fe43aebbc4d2ff9f7311bc" } } }:::
> current time is Tue Jul 2 21:09:09 2013
> Autoscale: Timer Event: Cloud-AutoScale-Timer-xxxxx-80
> Returning avg_val: 67
> If I look in CloudStack, I do see the deployVirtualMachine calls coming from the NetScaler during the scale up, but I don't see any destroyVirtualMachine hitting the server for the scale down.
--
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