cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "prashant kumar mishra (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CLOUDSTACK-1622) Global parameter "cluster.memory.allocated.capacity.disablethreshold" is not disabling cluster after threshold value
Date Fri, 17 May 2013 10:45:15 GMT

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

prashant kumar mishra updated CLOUDSTACK-1622:
----------------------------------------------

    Description: 
Cluster should get  disable after used memory crosses threshold of global parameter cluster.memory.allocated.capacity.disablethreshold
.

Steps to repo
-------------------
1-set cluster level parameter  cluster.memory.allocated.capacity.disablethreshold  to blank
space
2-Set Global parameter cluster.memory.allocated.capacity.disablethreshold  to some value in
my case 0.2
3-Deploy vms

Expected
----------------
After threshold value (0.2) cluster should get disable

Actual
---------
Cluster is not getting disable




  was:
1-ASF Master branch 
2-Hypervisor=Xen

Cluster should get  disable after used memory crosses threshold of global parameter cluster.memory.allocated.capacity.disablethreshold
 ,






    
> Global parameter "cluster.memory.allocated.capacity.disablethreshold"  is not disabling
cluster after threshold value
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-1622
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1622
>             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: apilog.log, cloud-backup.dmp, management-server.log, screenshot-1.jpg,
screenshot-2.jpg
>
>
> Cluster should get  disable after used memory crosses threshold of global parameter cluster.memory.allocated.capacity.disablethreshold
.
> Steps to repo
> -------------------
> 1-set cluster level parameter  cluster.memory.allocated.capacity.disablethreshold  to
blank space
> 2-Set Global parameter cluster.memory.allocated.capacity.disablethreshold  to some value
in my case 0.2
> 3-Deploy vms
> Expected
> ----------------
> After threshold value (0.2) cluster should get disable
> Actual
> ---------
> Cluster is not getting disable

--
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