You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2013/06/12 11:34:21 UTC

[jira] [Commented] (CLOUDSTACK-1622) Global parameter "cluster.memory.allocated.capacity.disablethreshold" is not disabling cluster after threshold value

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-1622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13681070#comment-13681070 ] 

ASF subversion and git services commented on CLOUDSTACK-1622:
-------------------------------------------------------------

Commit a30f9fa64a49acfe7d3ac57f2ef9d890473f48c4 in branch refs/heads/master from [~harikrishna.patnala]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=a30f9fa ]

Fix for CLOUDSTACK-1704 and CLOUDSTACK-1622

Signed-off-by: Abhinandan Prateek <ap...@apache.org>

                
> 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
>            Assignee: Harikrishna Patnala
>             Fix For: 4.2.0
>
>         Attachments: logs.rar
>
>
> Cluster should get  disable after alocated memory crosses threshold of global parameter cluster.memory.allocated.capacity.disablethreshold .
> ->-->when i set "cluster.memory.allocated.capacity.disablethreshold" to blank character at cluster level , Global parameter"cluster.memory.allocated.capacity.disablethreshold" stop working. 
> Steps to repo
> -------------------
> 1-Set Global parameter cluster.memory.allocated.capacity.disablethreshold  to some value say 0.3
> 2-set cluster level parameter  cluster.memory.allocated.capacity.disablethreshold  to blank space
> 3-Deploy vms
> Expected
> ----------------
> After threshold value (0.3) 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