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.
Thanks, -Nitin On 09/01/15 4:07 AM, "David Williams" <david.willi...@interoute.com> 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 >releases? > >Thanks, > >Dave > >
