Return-Path: X-Original-To: apmail-activemq-users-archive@www.apache.org Delivered-To: apmail-activemq-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 0C36A10978 for ; Wed, 12 Feb 2014 10:38:50 +0000 (UTC) Received: (qmail 96810 invoked by uid 500); 12 Feb 2014 10:38:49 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 94858 invoked by uid 500); 12 Feb 2014 10:38:44 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 94706 invoked by uid 99); 12 Feb 2014 10:38:37 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 Feb 2014 10:38:37 +0000 X-ASF-Spam-Status: No, hits=-5.0 required=5.0 tests=RCVD_IN_DNSWL_HI,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of tmielke@redhat.com designates 209.132.183.28 as permitted sender) Received: from [209.132.183.28] (HELO mx1.redhat.com) (209.132.183.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 Feb 2014 10:38:31 +0000 Received: from int-mx02.intmail.prod.int.phx2.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id s1CAc8Jb032043 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Wed, 12 Feb 2014 05:38:09 -0500 Received: from [10.36.7.42] (vpn1-7-42.ams2.redhat.com [10.36.7.42]) by int-mx02.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id s1CAc6lK018829 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Wed, 12 Feb 2014 05:38:08 -0500 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) Subject: Re: KahaDb cleanUp interval From: Torsten Mielke In-Reply-To: <1392199804191-4677852.post@n4.nabble.com> Date: Wed, 12 Feb 2014 11:38:07 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <934ED5DB-F24A-43FF-9B3A-E137CF2F9CFC@redhat.com> References: <1391005755121-4676946.post@n4.nabble.com> <1391059083305-4676998.post@n4.nabble.com> <1391490455249-4677373.post@n4.nabble.com> <1392199804191-4677852.post@n4.nabble.com> To: users X-Scanned-By: MIMEDefang 2.67 on 10.5.11.12 X-Virus-Checked: Checked by ClamAV on apache.org Hello, If you increase the cleanup interval to 60 secs there may perhaps be = more cleanup work to be done by the task and it may take slightly longer = to run. However I doubt you would notice any impact, it should work just = like before.=20 Nevertheless you should test it accordingly in load test that simulates = your production load.=20 Regards, Torsten Mielke tmielke.blogspot.com On 12 Feb 2014, at 11:10 am, khandelwalanuj = wrote: Hi,=20 By Default KahaDb cleanupInterval is 30 seconds. I think this is very = small duration for cleanup. For broker with heavy load this interval is = very small. So I want to increase this value to 60 seconds.=20 What is the impect on the broker by increasing this value to 60 seconds = ?=20 Thansk,=20 Anuj