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

ASF GitHub Bot commented on CLOUDSTACK-9667:
--------------------------------------------

GitHub user bvbharatk opened a pull request:

    https://github.com/apache/cloudstack/pull/1969

    CLOUDSTACK-9667 Enable resourcecount.check.interval by default

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/bvbharatk/cloudstack CLOUDSTACK-9667

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cloudstack/pull/1969.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1969
    
----
commit 0ef668b3d2f62bb94ce8ac95b8e315214b506c62
Author: Bharat Kumar <[email protected]>
Date:   2015-10-06T11:00:58Z

    CLOUDSTACK-9667 Enable resourcecount.check.interval by default

----


> Enable resourcecount.check.interval by default
> ----------------------------------------------
>
>                 Key: CLOUDSTACK-9667
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9667
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: Management Server
>    Affects Versions: 4.9.0
>            Reporter: Bharat Kumar
>            Assignee: Bharat Kumar
>             Fix For: 4.9.2.0
>
>
> Issue. In cloud stack there is a thread with runs at regular interval and 
> updates the resource count. The interval at with this runs is specified by 
> resourcecount.check.interval global config. This is set to zero by default, 
> which means it will never run and so the count of public Ips is not updated.
> Fix: Made the default value 300 seconds. This will run the resource count 
> update thread thread every 300 seconds by default.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to