activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rural Hunter (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-6203) KahaDB: Allow rewrite of message acks in older logs which prevent cleanup
Date Thu, 26 May 2016 14:06:12 GMT

    [ https://issues.apache.org/jira/browse/AMQ-6203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15302109#comment-15302109
] 

Rural Hunter commented on AMQ-6203:
-----------------------------------

I tried 5.13.3. But it seems the compaction actualy can never start under heavy load(such
as our production) as I always see this log:
2016-05-26 21:47:36,153 | TRACE | Journal activity detected, no Ack compaction scheduled.
|org.apache.activemq.store.kahadb.MessageDatabase | ActiveMQ Journal Checkpoint Worker

> KahaDB: Allow rewrite of message acks in older logs which prevent cleanup
> -------------------------------------------------------------------------
>
>                 Key: AMQ-6203
>                 URL: https://issues.apache.org/jira/browse/AMQ-6203
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: KahaDB
>    Affects Versions: 5.13.0, 5.13.1, 5.12.3, 5.13.2
>            Reporter: Timothy Bish
>            Assignee: Timothy Bish
>             Fix For: 5.14.0, 5.13.3
>
>
> There are cases where a chain of journal logs can grow due to acks for messages in older
logs needing to be kept so that on recovery proper state can be restored and older messages
not be resurrected.  
> In many cases just moving the acks from one log forward to a new log can free an entire
chain during subsequent GC cycles.  The 'compacted' ack log can be written during the time
between GC cycles without the index lock being held meaning normal broker operations can continue.
 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message