cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Somesh Naidu <>
Subject RE: Global setting resourcecount.check.interval default of 0
Date Tue, 13 Jan 2015 18:16:03 GMT
Yeah, I don't think we should continue to keep the default configuration to not run this automatically.
This process might consume additional resources on mgmt. server. From experience I haven't
seen many complain about the resource count so this may not be an issue for all. So running
this by default would effectively waste valuable system resources. Also note that this activity
can also be triggered per domain/account manually from the UI.

Either way, it shouldn't be a big deal since the value is configurable and can be set to any
value desired by the administrator.

-----Original Message-----
From: Nitin Mehta [] 
Sent: Friday, January 09, 2015 2:30 PM
Subject: Re: Global setting resourcecount.check.interval default of 0

IIRC it was put in for sanity reasons. Many a times we found (because of
bugs) that the resource count of MS went out of sync with the actual count
and the user coundnt create further resources or create more than allowed.
This was kept for re syncing the count with the actual count. You are free
to keep to whatever value you deem is right as per the frequency of
resource creation in your cloud.


On 09/01/15 4:07 AM, "David Williams" <> wrote:

>Hi all,
>We have noticed that the global setting resourcecount.check.interval has
>a default of 0 which according to the description, means never run:
>      | category |               name               |           value
>       |          
>                                              description
>      | Advanced |   resourcecount.check.interval   |             0
>       |          
>Time (in seconds) to wait before retrying resource count check task.
>Default is 0 which is to never run the task
>Does anyone know why this global setting is needed? I mean, why does
>cloudstack not keep the counts up to date and correct anyway.
>Does anyone know why the default value is 0 (never run)?
>Can the default be set to something like 3600 instead of 0 in future

View raw message