[
https://issues.apache.org/jira/browse/CLOUDSTACK-3187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13692964#comment-13692964
]
Harikrishna Patnala commented on CLOUDSTACK-3187:
-------------------------------------------------
In review board https://reviews.apache.org/r/12078/
> cluster.(cpu/memory).allocated.capacity.disablethreshold in not considering
> overcommit factor;cluster is getting disable based on actual use
> ---------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-3187
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3187
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: 4.2.0
> Reporter: prashant kumar mishra
> Assignee: Harikrishna Patnala
> Priority: Critical
> Fix For: 4.2.0
>
> Attachments: DB_Logs.rar
>
>
> Steps to reproduce
> ---------------------------
> 1-set "cluster.(cpu/mem).allocated.capacity.disablethreshold" to 0.75
> 2-set (memory/cpu) overcommit ratio to 2
> 3-Try to use capacity(cpu/ram) more than what actual available by deploying
> some vms
> Actual
> ---------
> Cluster is getting disabled after actual usage crosses(0.75) disable threshold
> Expected
> --------------
> cluster should get disabled based on over committed use not actual use
> Logs
> --------
> 2013-06-25 10:11:49,573 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-7:job-19) Listing clusters in order of aggregate capacity, that
> have (atleast one host with) enough CPU and RAM capacity under this Zone: 1
> 2013-06-25 10:11:49,593 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-7:job-19) Cannot allocate cluster list [1] for vm creation
> since their allocated percentage crosses the disable capacity threshold
> defined at each cluster/ at global value for capacity Type : 0, skipping
> these clusters
> 2013-06-25 10:11:49,594 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-7:job-19) No clusters found after removing disabled clusters
> and clusters in avoid list, returning.
> 2013-06-25 10:11:49,601 DEBUG [cloud.vm.UserVmManagerImpl]
> (Job-Executor-7:job-19) Destroying vm VM[User|mm4] as it failed to create on
> Host with Id:null
> 2013-06-25 10:11:49,630 DEBUG [cloud.capacity.CapacityManagerImpl]
> (Job-Executor-7:job-19) VM state transitted from :Stopped to Error with
> event: OperationFailedToErrorvm's original host id: null new host id: null
> host id before state transition: null
> 2013-06-25 10:11:49,654 WARN [apache.cloudstack.alerts]
> (Job-Executor-7:job-19) alertType:: 8 // dataCenterId:: 1 // podId:: null //
> clusterId:: null // message:: Failed to deploy Vm with Id: 8, on Host with
> Id: null
> 2013-06-25 10:11:49,726 INFO [user.vm.DeployVMCmd] (Job-Executor-7:job-19)
> com.cloud.exception.InsufficientServerCapacityException: Unable to create a
> deployment for VM[User|mm4]Scope=interface com.cloud.dc.DataCenter; id=1
> 2013-06-25 10:11:49,727 INFO [user.vm.DeployVMCmd] (Job-Executor-7:job-19)
> Unable to create a deployment for VM[User|mm4]
> com.cloud.exception.InsufficientServerCapacityException: Unable to create a
> deployment for VM[User|mm4]Scope=interface com.cloud.dc.DataCenter; id=1
> at
> org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.reserveVirtualMachine(VMEntityManagerImpl.java:212)
> at
> org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.reserve(VirtualMachineEntityImpl.java:198)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3312)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2851)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2837)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
> at
> com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:679)
> 2013-06-25 10:11:49,729 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-7:job-19) Complete async job-19, jobStatus: 2, resultCode: 530,
> result: Error Code: 533 Error text: Unable to create a deployment for
> VM[User|mm4]
> 2013-06-25 10:11:51,073 DEBUG [agent.manager.AgentManagerImpl]
> (AgentManager-Handler-2:null) Ping from 3
--
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
