Sorry. I answered the wrong question. The LevelDB recovery does seem to be
a function of number of queues and number of outstanding messages.
On Sun, Feb 1, 2015 at 2:44 PM, artnaseef wrote:
> Are the recovery times related to the number of messages stored in LevelDB
> at
> startup? I've seen
Yes. My fault! I just realized I transposed email threads by accident.
I have two problems.. one is the queue GC on startup and the other is lack
of any message when the broker is doing leveldb recovery.
On Mon, Feb 2, 2015 at 6:00 AM, Tim Bain wrote:
> That thread dump shows you in LevelDB
That thread dump shows you in LevelDB doing message replay, not destination
GC; are you sure destination GC is to blame for this particular issue? And
do you know how many messages were in LevelDB at startup?
Thanks.
I’m unsure as we still have to use KahaDB for scheduled messages. So there
are
Thanks.
I’m unsure as we still have to use KahaDB for scheduled messages. So there
are definitely a ton there.
but it seems to be the total number of empty queues that get GCd on startup.
I was keeping a consumer on some of the ephemeral queues, which prevented
them from getting GCd. Then when
Are the recovery times related to the number of messages stored in LevelDB at
startup? I've seen KahaDB startup take a long time when there are a large
number of messages stored.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/RFE-print-that-LevelDB-is-doing-a-recovery-t
OK. Created.
https://issues.apache.org/jira/browse/AMQ-5556
On Sun, Feb 1, 2015 at 6:21 AM, Tim Bain wrote:
> Kevin,
>
> This sounds like a reasonable enhancement; can you submit it via JIRA?
>
> Having a log line when you start and finish recovery sounds easy to do,
> though have you checked
Great. I”ll submit an RFE today. (about to go for a walk).
The recovery I just did was taking up to an hour so I just killed it.
My startup times are taking a while so I’m trying to step through and
figure out at what places we need to tighten up ship to make things a bit
easier to manage!
Than
Kevin,
This sounds like a reasonable enhancement; can you submit it via JIRA?
Having a log line when you start and finish recovery sounds easy to do,
though have you checked that there isn't already one at DEBUG or TRACE?
(INFO does seem like the right level, though.)
Logging percent complete wo
