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) parameter "cluster.memory.allocated.capacity.disablethreshold" is not disabling cluster after threshold value
Date Mon, 11 Mar 2013 11:05:12 GMT

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

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

    Attachment: screenshot-1.jpg
    
> 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
>            Assignee: Bharat Kumar
>             Fix For: 4.2.0
>
>         Attachments: screenshot-1.jpg, screenshot-2.jpg
>
>
> 1-ASF Master branch 
> 2-Hypervisor=Xen
> Cluster should get  disable after used memory crosses threshold of cluster.memory.allocated.capacity.disablethreshold
 ,
> DB
> -----
> -----
> mysql> select * from configuration where name="cluster.memory.allocated.capacity.disablethreshold"\G;
> *************************** 1. row ***************************
>    category: Alert
>    instance: DEFAULT
>   component: management-server
>        name: cluster.memory.allocated.capacity.disablethreshold
>       value: 0.5
> description: Percentage (as a value between 0 and 1) of memory utilization above which
allocators will disable using the cluster for low memory available. Keep the corresponding
notification threshold lower than this to be notified beforehand.
> 1 row in set (0.00 sec)
> ERROR:
> No query specified
> --------------------------------------------
> mysql> select * from op_host_capacity where host_id=1\G;
> *************************** 1. row ***************************
>                id: 12
>           host_id: 1
>    data_center_id: 1
>            pod_id: 1
>        cluster_id: 1
>     used_capacity: 14361296896
> reserved_capacity: 0
>    total_capacity: 16190157312
>     capacity_type: 0
>    capacity_state: Enabled
>       update_time: 2013-03-11 09:49:06
>           created: 2013-03-11 07:23:17
> *************************** 2. row ***************************
>                id: 13
>           host_id: 1
>    data_center_id: 1
>            pod_id: 1
>        cluster_id: 1
>     used_capacity: 3900
> reserved_capacity: 0
>    total_capacity: 9576
>     capacity_type: 1
>    capacity_state: Enabled
>       update_time: 2013-03-11 09:49:06
>           created: 2013-03-11 07:23:17
> 2 rows in set (0.00 sec)
> ERROR:
> No query specified
> -----------------------------------------------------------------------------------------
> mysql> select * from cluster_details where cluster_id=8;
> +----+------------+-----------------------+-------+
> | id | cluster_id | name                  | value |
> +----+------------+-----------------------+-------+
> | 15 |          8 | cpuOvercommitRatio    | 1.0   |
> | 16 |          8 | memoryOvercommitRatio | 1.0   |
> +----+------------+-----------------------+-------+

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