cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Harikrishna Patnala (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CLOUDSTACK-3365) cluster level parameters cluster.(cpu/memory).allocated.capacity.notificationthreshold is not considering overcommit value
Date Wed, 10 Jul 2013 06:21:48 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-3365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Harikrishna Patnala updated CLOUDSTACK-3365:
--------------------------------------------

    Status: Ready To Review  (was: In Progress)
    
> 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
>            Assignee: Harikrishna Patnala
>             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

Mime
View raw message