From users-return-19839-apmail-cloudstack-users-archive=cloudstack.apache.org@cloudstack.apache.org Fri Jan 9 19:30:10 2015 Return-Path: X-Original-To: apmail-cloudstack-users-archive@www.apache.org Delivered-To: apmail-cloudstack-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4026B10B58 for ; Fri, 9 Jan 2015 19:30:10 +0000 (UTC) Received: (qmail 88200 invoked by uid 500); 9 Jan 2015 19:30:10 -0000 Delivered-To: apmail-cloudstack-users-archive@cloudstack.apache.org Received: (qmail 88155 invoked by uid 500); 9 Jan 2015 19:30:10 -0000 Mailing-List: contact users-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@cloudstack.apache.org Delivered-To: mailing list users@cloudstack.apache.org Received: (qmail 88071 invoked by uid 99); 9 Jan 2015 19:30:04 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Jan 2015 19:30:04 +0000 X-ASF-Spam-Status: No, hits=-2.3 required=5.0 tests=RCVD_IN_DNSWL_MED,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of Nitin.Mehta@citrix.com designates 185.25.65.24 as permitted sender) Received: from [185.25.65.24] (HELO SMTP.EU.CITRIX.COM) (185.25.65.24) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Jan 2015 19:29:39 +0000 X-IronPort-AV: E=Sophos;i="5.07,732,1413244800"; d="scan'208";a="28521585" From: Nitin Mehta To: "users@cloudstack.apache.org" Subject: Re: Global setting resourcecount.check.interval default of 0 Thread-Topic: Global setting resourcecount.check.interval default of 0 Thread-Index: AdAsBHurYfBBITXvRiqHPPtB/UUs2f//cAOA Date: Fri, 9 Jan 2015 19:29:36 +0000 Message-ID: In-Reply-To: <9B3B2E4F79F7A14B990E92C561CC1610A40EFC3F@CZPREXMBX01.interoute.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.2.0.120402 Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-DLP: AMS1 X-Virus-Checked: Checked by ClamAV on apache.org 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" 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 > | =20 > description > | Advanced | resourcecount.check.interval | 0 > | =20 >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 > >