activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Posta <christian.po...@gmail.com>
Subject Re: PerDestination KahaDB and slow recovery
Date Mon, 20 May 2013 21:22:03 GMT
 It's indeed sequential, and I bet this can be improved. Open a jira and we
can track it.


On Mon, May 20, 2013 at 1:48 PM, Oleg Dulin <oleg.dulin@gmail.com> wrote:

> Dear Colleagues:
>
> We have about 1500 queues on the broker. Some queues are consumed in a
> "batch" fashion. So the journal gets fragmented and becomes quite large. To
> optimize disk usage, I've done the following:
>
>             <persistenceAdapter>
>                 <mKahaDB directory="activemq-data/**kahadb">
>                        <filteredPersistenceAdapters>
>                                  <filteredKahaDB perDestination="true" >
>                                        <persistenceAdapter>
>                                                <kahaDB
> journalMaxFileLength="16mb" cleanupInterval="10000"/>
>                                        </persistenceAdapter>
>                                  </filteredKahaDB>
>                        </filteredPersistenceAdapters>
>                 </mKahaDB>
>                </persistenceAdapter>
>
>
> However, now the broker restart becomes really slow because it seems to do
> recovery sequentially on each journal.
>
> Is there a way to speed this up ?
>
> Help is greatly appreciated.
>
>
> --
> Regards,
> Oleg Dulin
> http://www.olegdulin.com
>
>
>


-- 
*Christian Posta*
http://www.christianposta.com/blog
twitter: @christianposta

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message