[
https://issues.apache.org/jira/browse/CLOUDSTACK-9650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15734743#comment-15734743
]
ASF GitHub Bot commented on CLOUDSTACK-9650:
--------------------------------------------
Github user wido commented on the issue:
https://github.com/apache/cloudstack/pull/1812
So to get this clear, you might OOM hypervisors due to this since you
allocate more memory on them?
Or is this just the cluster threshold and it still might not find a
suitable hypervisor
> Allow starting VMs regardless of cpu/memory cluster.disablethreshold setting
> ----------------------------------------------------------------------------
>
> Key: CLOUDSTACK-9650
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9650
> Project: CloudStack
> Issue Type: Improvement
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: 4.10.0.0
> Reporter: Koushik Das
> Assignee: Koushik Das
> Fix For: 4.10.1.0
>
>
> VM deployments are not allowed on clusters where resource (cpu/memory)
> allocation has exceeded the cluster disabled thresholds. The same policy also
> gets applied in case of start VM if last host where the VM was running
> doesn't have enough capacity and a new host is picked up. In certain
> scenarios this can be restrictive and despite having capacity, the VM cannot
> be started.
> This improvement is to provide administrator an option to disable/enable
> cluster threshold enforcement during start of a stopped VM as long as
> sufficient capacity is available.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
