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 404A01054C for ; Wed, 12 Feb 2014 15:45:24 +0000 (UTC) Received: (qmail 71369 invoked by uid 500); 12 Feb 2014 15:45:22 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 71294 invoked by uid 500); 12 Feb 2014 15:45:19 -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 71285 invoked by uid 99); 12 Feb 2014 15:45:16 -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 15:45:16 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of christian.posta@gmail.com designates 209.85.217.171 as permitted sender) Received: from [209.85.217.171] (HELO mail-lb0-f171.google.com) (209.85.217.171) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 Feb 2014 15:45:11 +0000 Received: by mail-lb0-f171.google.com with SMTP id c11so7158110lbj.2 for ; Wed, 12 Feb 2014 07:44:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=0l6WxtgsoWl9d4UoS0Otch3opThrwdV/gH4kXoFIaGQ=; b=ONvmf2dacq/dnsqV1vSmNb08hOCGxk8cEA1hvEx4UShV4T1FhK6yKD2V8vZVzQQ7Xq gpxGCT2oK8BQX17iWGvnBylHjzAid8Jhy2/Tkn61mVfUMGq7FWEtalzNp5bCEAavi5Go bpb75MShbMY3oLNKW5XiZj9i6+s6JFbhfoaeuRURdemCSVkyl/hMv7w3/ermvmBFZ540 ZGuY6JqOm6+lRDRWDXRWeeJNfhLY4A8q9j1fFuv8QOQ891ZpXBhiFK8v/iRs4foelkpI 1e9nVJ5V6382RSKLbMWmLxS4CP6KMHXhV2CqV9VvKPB7f64bx/sGA1e4zXtzhGXek7DD v6Fg== MIME-Version: 1.0 X-Received: by 10.152.234.36 with SMTP id ub4mr32272751lac.13.1392219890825; Wed, 12 Feb 2014 07:44:50 -0800 (PST) Received: by 10.114.1.174 with HTTP; Wed, 12 Feb 2014 07:44:50 -0800 (PST) In-Reply-To: <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> <934ED5DB-F24A-43FF-9B3A-E137CF2F9CFC@redhat.com> Date: Wed, 12 Feb 2014 08:44:50 -0700 Message-ID: Subject: Re: KahaDb cleanUp interval From: Christian Posta To: "users@activemq.apache.org" Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org IIRC, the counts/sizes for StoreUsage (what's currently used) won't be as consistent the longer your cleanup period is... eg.. if you take 5 mins to cleanup, your may hit producer flow control on store if the store usage isn't updated correctly even though all your messages may have been consumed. On Wed, Feb 12, 2014 at 3:38 AM, Torsten Mielke wrote: > 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. > > Nevertheless you should test it accordingly in load test that simulates your production load. > > Regards, > > Torsten Mielke > tmielke.blogspot.com > > > > On 12 Feb 2014, at 11:10 am, khandelwalanuj wrote: > > Hi, > > 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. > > What is the impect on the broker by increasing this value to 60 seconds ? > > Thansk, > Anuj > > -- Christian Posta http://www.christianposta.com/blog twitter: @christianposta