Return-Path: X-Original-To: apmail-incubator-cloudstack-issues-archive@minotaur.apache.org Delivered-To: apmail-incubator-cloudstack-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 408A9E511 for ; Mon, 18 Mar 2013 07:14:16 +0000 (UTC) Received: (qmail 10827 invoked by uid 500); 18 Mar 2013 07:14:16 -0000 Delivered-To: apmail-incubator-cloudstack-issues-archive@incubator.apache.org Received: (qmail 10797 invoked by uid 500); 18 Mar 2013 07:14:15 -0000 Mailing-List: contact cloudstack-issues-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cloudstack-dev@incubator.apache.org Delivered-To: mailing list cloudstack-issues@incubator.apache.org Received: (qmail 10783 invoked by uid 99); 18 Mar 2013 07:14:15 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 Mar 2013 07:14:15 +0000 Date: Mon, 18 Mar 2013 07:14:15 +0000 (UTC) From: "prashant kumar mishra (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CLOUDSTACK-1704) allocatore is not disabling cluster after the threshold value, set in "cluster.cpu.allocated.capacity.disablethreshold" 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-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-1704: ---------------------------------------------- Attachment: screenshot-1.jpg > allocatore is not disabling cluster after the threshold value, set in "cluster.cpu.allocated.capacity.disablethreshold" > ----------------------------------------------------------------------------------------------------------------------- > > Key: CLOUDSTACK-1704 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1704 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the default.) > Affects Versions: 4.2.0 > Reporter: prashant kumar mishra > Fix For: 4.2.0 > > Attachments: screenshot-1.jpg, screenshot-2.jpg > > > "cluster.cpu.allocated.capacity.disablethreshold "Percentage (as a value between 0 and 1) of cpu utilization above which allocators will disable using the cluster for low cpu available. Keep the corresponding notification threshold lower than this to be notified beforehand. > Hypervisor "xen" > Branch "Master" > Steps to reproduce > ---------------------------- > 1-Set cluster.cpu.allocated.capacity.disablethreshold to 0.5 , > 2-Restart MS > 3-Deploy some vms , so that cpu utilizatio should be >0.5 > Expected > ------------- > Cluster should be disabled by allocator after threshold value > Actual > ----------- > Allocator is not disabling cluster after threshold value -- 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