Return-Path: X-Original-To: apmail-cloudstack-issues-archive@www.apache.org Delivered-To: apmail-cloudstack-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B0BA1105F1 for ; Fri, 9 Aug 2013 07:08:50 +0000 (UTC) Received: (qmail 62860 invoked by uid 500); 9 Aug 2013 07:08:49 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 62768 invoked by uid 500); 9 Aug 2013 07:08:49 -0000 Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list issues@cloudstack.apache.org Received: (qmail 62754 invoked by uid 500); 9 Aug 2013 07:08:48 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 62750 invoked by uid 99); 9 Aug 2013 07:08:48 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Aug 2013 07:08:48 +0000 Date: Fri, 9 Aug 2013 07:08:48 +0000 (UTC) From: "prashant kumar mishra (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Closed] (CLOUDSTACK-3365) cluster level parameters cluster.(cpu/memory).allocated.capacity.notificationthreshold is not considering overcommit value MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CLOUDSTACK-3365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra closed CLOUDSTACK-3365. --------------------------------------------- passed > 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