Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <27502591.post@talk.nabble.com>
Date: Mon, 8 Feb 2010 08:38:40 -0800 (PST)
From: "B.D." <boris.dainson@gmail.com>
To: users@activemq.apache.org
Subject: Re: KahaDB data files not cleaned up
In-Reply-To: <27441942.post@talk.nabble.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
References: <27441942.post@talk.nabble.com>


Any suggestions on how to prevent pileups of data/kahadb/db-xxx.log files?=
=20

I just had to clean up 301 data/kahadb/db-xxx.log files that accumulated on
a QA machine over 6 days. Message time to live is one day so that should no=
t
be happening.=20

Logs show KahaDB cleanup was taking longer than expected:=20
activemq.log:2010-02-08 13:31:29,664 | INFO  | Slow KahaDB access: cleanup
took 591 | org.apache.activemq.store.kahadb.MessageDatabase | ActiveMQ
Journal Checkpoint Worker


Thanks


B.D. wrote:
>=20
> Hi,
>=20
> I=E2=80=99m using ActiveMQ 5.3 with KahaDB. Two brokers are in a network =
with
> failover. Publishers are sending messages to a composite destination that
> forwards to a topic or a queue.  It works ok with topics but with queues
> after a while there is accumulation of db-xxx.log files in the data/kahad=
b
> directory.=20
>=20
> Files will be several days old despite the fact that all messages have a
> one-day time to live. Dead letter strategy is individualDeadLetterStrateg=
y
> with processExpired=3D"false" so I do not expect expired messages to stay
> around in any form. Purging queues using admin console does not get rid o=
f
> these files. The only way I found to clean it up was to stop the broker
> and clean up the whole data directory.=20
>=20
> I could reproduce this problem in a test setup by starting/stopping
> brokers, publishers and subscribers. Older data/kahadb/db-X.log files are
> normally getting deleted but some are not, see below. In these tests
> time-to-live on all messages was 10 minutes so this should not be
> happening. See directory lists below.
>=20
> With a single broker I could not reproduce that same problem. Older
> db-X.log files were always eventually getting cleaned up. However I
> noticed that db.data file can grow. It reached 360M while it normally
> stays below 34M.
>=20
> Any suggestion how to prevent growth of files in the data/kahadb
> directory?=20
>=20
> Thanks,
>=20
>=20
> Broker 1 in a 2-broker network:=20
> 33555255=092010-01-07=0923:18:13=09data/kahadb/db-80.log
> 33030144=092010-01-08=0907:46:16=09data/kahadb/db-177.log
> 33554509=092010-01-07=0922:50:21=09data/kahadb/db-74.log
> 33555184=092010-01-08=0901:34:55=09data/kahadb/db-110.log
> 33554441=092010-01-07=0922:41:00=09data/kahadb/db-72.log
> 33554519=092010-01-08=0904:40:53=09data/kahadb/db-144.log
> 33554522=092010-01-07=0919:51:33=09data/kahadb/db-34.log
> 33555005=092010-01-08=0904:09:10=09data/kahadb/db-138.log
> 33555019=092010-01-08=0902:07:52=09data/kahadb/db-117.log
> 33554494=092010-01-07=0918:52:05=09data/kahadb/db-21.log
> 33555122=092010-01-08=0904:30:02=09data/kahadb/db-142.log
> 3287296=092010-01-08=0907:46:16=09data/kahadb/db.redo
> 33554733=092010-01-08=0900:40:15=09data/kahadb/db-98.log
> 33554703=092010-01-08=0907:34:38=09data/kahadb/db-175.log
> 33554997=092010-01-08=0907:26:41=09data/kahadb/db-174.log
> 10763=092010-01-08=0907:46:16=09data/kahadb/db.free
> 33555298=092010-01-07=0923:04:18=09data/kahadb/db-77.log
> 33554537=092010-01-07=0923:45:26=09data/kahadb/db-86.log
> 23187456=092010-01-08=0907:46:16=09data/kahadb/db.data
> 33555022=092010-01-08=0902:52:40=09data/kahadb/db-125.log
>=20
>=20
> Broker 2 in a 2-broker network:=20
> 33030144=092010-01-08=0907:46:15=09data/kahadb/db-172.log
> 1756504=092010-01-08=0912:07:34=09data/kahadb/db.redo
> 33554527=092010-01-07=0918:29:16=09data/kahadb/db-3.log
> 33554595=092010-01-07=0917:49:28=09data/kahadb/db-1.log
> 0=09=092010-01-07=0916:25:00=09data/kahadb/lock
> 2543616=092010-01-08=0912:07:34=09data/kahadb/db.data
> 33554596=092010-01-07=0923:56:35=09data/kahadb/db-79.log
>=20
>=20
> Single broker (not a network):=20
> 33030144 =09Jan 14 18:25 db-1318.log
> 364490752 =09Feb  3 10:22 db.data
> 3287296 =09Feb  3 10:22 db.redo
> 0 =09=09Jan  8 12:33 lock
>=20
>=20

--=20
View this message in context: http://old.nabble.com/KahaDB-data-files-not-c=
leaned-up-tp27441942p27502591.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.