You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "prashant kumar mishra (JIRA)" <ji...@apache.org> on 2013/07/04 15:19:49 UTC
[jira] [Updated] (CLOUDSTACK-3365) cluster level parameters
cluster.(cpu/memory).allocated.capacity.notificationthreshold is not
considering overcommit value
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
prashant kumar mishra updated CLOUDSTACK-3365:
----------------------------------------------
Summary: cluster level parameters cluster.(cpu/memory).allocated.capacity.notificationthreshold is not considering overcommit value (was: cluster level parameter cluster.(cpu/memory).allocated.capacity.notificationthreshold is not considering overcommit value)
> cluster level parameters cluster.(cpu/memory).allocated.capacity.notificationthreshold is not considering overcommit value
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-3365
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3365
> 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
> Environment: master stable branch ;hypervisor xen
> Reporter: prashant kumar mishra
> Fix For: 4.2.0
>
> Attachments: Db_Logs.rar, screenshot-1.jpg
>
>
> Alerts for memory and cpu are getting generated based on actual usage .It should consider overcommit ratio
> Steps to reproduce
> ----------------------------
> 1-set cluster level parameter "cluster.cpu.allocated.capacity.notificationthreshold" to some value say 0.5
> 2-Set overcomimt ratio to 3 for cpu
> 2-deploy vm so that actual cpu usage should cross 0.5
> 3-Check alerts
> Expected
> -------------
> Alerts should get generated based on overcommited value
> Actual
> ---------
> Alerts are getting generated based on actual usage
> Logs
> -------
> 2013-07-04 14:26:54,567 DEBUG [cloud.alert.AlertManagerImpl] (CapacityChecker:null) Unallocated CPU is low, total: 9576 Mhz, used: 6500 Mhz (67.88%)
> 2013-07-04 14:26:54,567 WARN [apache.cloudstack.alerts] (CapacityChecker:null) alertType:: 1 // dataCenterId:: 1 // podId:: 1 // clusterId:: null // message:: System Alert: Low Unallocated CPU in cluster cluster pod pod of availability zone zone
>
--
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