Hi Rafael,
Our testing has shown that multi does use more resources for the same
throughput; more cpu, ram and storage, but not significantly more unless
you are already at the limit.
We have configured one-kaha-per-queue so it does improve the storage
reclaim when for whatever reason the reclaim
After a while of using the ActiveMQ with mKahadb it crashes with the
following errors:
2022-10-05 14:14:06,735 | WARN | Error subscribing to
/DvxSrv/12/Mine/Sampling |
org.apache.activemq.transport.mqtt.strategy.AbstractMQTTSubscriptionStrategy
| ActiveMQ Transport: tcp:///10.26.163.157:40380@188
As suggested by Mark Johnson I'm evaluating a multi-kahadb setup:
But, after that, I'm facing the following warning:
2022-10-04 18:05:23,555 | WAR
Hi Rafael,
Building on the reply from Marco, we have experienced the same issue with
queues and are evaluating a multi kahadb set up of a kahadb per queue.
Obviously this does increase the total number of files but so far we have
not seen any significant increase in total storage compared to a sin
Hello Marco,
First of All, Thanks for your reply and detailed explanation.
To avoid increasing the KahaDB with DLQ queues, we disable the DLQ, so
expired messages will be discarded automatically:
Because of that configuration, I assume that the problems fall on durable
topics.
As we know th
Hi Rafael,
I’m just an ActiveMQ classic user.
I will report the behavior of ActiveMQ I experienced.
As far as I know the ActiveMQ classic journal is composed of append only
files.
Each file should be by default 32MB in size (this can be changed, I think
is controlled by journalLogFileSize)
A jour
Hi Dears,
I'm using ActiveMQ 5.15.9 and after about one month our customers started
to complain about the Kahadb folder increase until reaching its limit and
crash the system. Then they delete the folder to recover the system, but we
are losing data in this process.
We activate the kahadb log and s
I would add that if you have a maintenance window available - a v. low
traffic time of day or week - where there are typically no persisted
messages, it is going to be least disruptive to use that time window to
perform an upgrade.
Copying across the store might not be necessary, in which case you
> time). It appears that the db-X.log files are not being removed even though
> all the messages in them have expired and are eligible for removal.
>
> Thanks,
> Steve
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Message-getting-stuck-on-topic-leading-to-KahaDB-log-files-not-being-deleted-and-disk-running-out-of-tp4703370p4703402.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
View this message in context:
http://activemq.2283324.n4.nabble.com/Message-getting-stuck-on-topic-leading-to-KahaDB-log-files-not-being-deleted-and-disk-running-out-of-tp4703370p4703402.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
ion.
>
> On Mon, Oct 26, 2015 at 8:40 AM, silvade wrote:
>
>> Hi,
>>
>> I am running into a problem where messages are getting stuck my topic,
>> leading to KahaDB log files not being deleted and disk running out of
>> space.
>>
>> The setup seem t
, Oct 26, 2015 at 8:40 AM, silvade wrote:
> Hi,
>
> I am running into a problem where messages are getting stuck my topic,
> leading to KahaDB log files not being deleted and disk running out of
> space.
>
> The setup seem to work fine for a week or so. When my durable subsc
Hi,
I am running into a problem where messages are getting stuck my topic,
leading to KahaDB log files not being deleted and disk running out of space.
The setup seem to work fine for a week or so. When my durable subscribers go
offline their messages are removed from the data.*.log after the
On 12/13/2013 01:02 PM, Andy Boothe [WCG] wrote:
Timothy,
Thank you for the quick response!
I had read that, but didn't see anything useful in it. Having re-read it,
I realize that my DLQs (which contain 100k messages) were a likely suspect
in keeping the log files "live." I cleared the DLQs, a
Timothy,
Thank you for the quick response!
I had read that, but didn't see anything useful in it. Having re-read it,
I realize that my DLQs (which contain 100k messages) were a likely suspect
in keeping the log files "live." I cleared the DLQs, and ActiveMQ
diligently deleted most of the log file
;t be getting cleaned up?
Thanks everyone in advance for your attention and help! And thank you
ActiveMQ devs for such a wonderful product! :)
*Andy Boothe*
Have you referenced this documentation:
http://activemq.apache.org/why-do-kahadb-log-files-remain-after-cleanup.html
-
Hello,
I have an ActiveMQ instance that has been running nicely for a couple of
months, but doesn't seem to clean up its KahaDB logs like I expect it to. (More
specifically, I expect to have like 1 log file, but in reality I have ~1500 log
files with 49G of data.)
ActiveMQ has processed about
, February 15, 2013 2:04 PM
> To: users@activemq.apache.org
> Subject: RE: Kahadb log files.
>
> Shaun,
>
> We are having similar issues. Did you ultimately delete the old log files?
> Or were you able to somehow close the loop on the old transactions.
>
> After running f
http://activemq.2283324.n4.nabble.com/Kahadb-log-files-tp4653202p4663561.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
com/Utility-to-debug-KahaDB-log-files-tp4660461.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
riginal Message-
From: Erickson, Shaun T.
Thanks, Gary. I'll do that.
-Original Message-
From: Gary Tully [mailto:gary.tu...@gmail.com]
have a read of:
http://activemq.apache.org/why-do-kahadb-log-files-remain-after-cleanup.html
and try out the trace level logging
On 12 June 2012
Thanks, Gary. I'll do that.
-Original Message-
From: Gary Tully [mailto:gary.tu...@gmail.com]
have a read of:
http://activemq.apache.org/why-do-kahadb-log-files-remain-after-cleanup.html
and try out the trace level logging
On 12 June 2012 16:16, wrote:
> We have many files l
have a read of:
http://activemq.apache.org/why-do-kahadb-log-files-remain-after-cleanup.html
and try out the trace level logging
On 12 June 2012 16:16, wrote:
> We have many files like this, under the kahadb directory:
>
> -rw-r--r-- 1 activemq activemq 33560615 Jun 5 19:03 db-545.l
We have many files like this, under the kahadb directory:
-rw-r--r-- 1 activemq activemq 33560615 Jun 5 19:03 db-545.log
My co-admin would like to know if they can all (or at least the older ones) be
blown away.
I'd like to know what they are, first, and how they can/should be handled,
before
We continue to see the same issue with 5.4.2, is this bug fixed?
On Wed, Nov 24, 2010 at 9:21 AM, Matt wrote:
> We have around ~1000 queues with currently no messages, but I have 249
> db*.log files in the kahadb directory dating from Sept 06 (when the mq
> process was started).
>
> It looks lik
We have around ~1000 queues with currently no messages, but I have 249
db*.log files in the kahadb directory dating from Sept 06 (when the mq
process was started).
It looks like we're seeing the same issue as below.
http://activemq.2283324.n4.nabble.com/storeUsage-with-kahaDB-which-files-td3034710
ext:
http://old.nabble.com/KahaDB-.log-files-are-not-cleaned-up-tp28340957p28340957.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
27 matches
Mail list logo
