[jira] [Commented] (AMQ-6203) KahaDB: Allow rewrite of message acks in older logs which prevent cleanup

["Jeff Genender (JIRA)" <ji...@apache.org>]

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

Jeff Genender commented on AMQ-6203:
------------------------------------

This actually looks like its related to AMQ-5695. Any reason why this wasn't back ported to the aforementioned version branch? If this truly does fix up those versions, this is a good candidate to be in 5.13.x.  I also believe this affects 5.11.x, 5.12. as well.  See AMQ-5695 for details.

> 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
>
>
> 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)