[ https://issues.apache.org/jira/browse/AMQ-6203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15232570#comment-15232570 ]
Christopher L. Shannon commented on AMQ-6203: --------------------------------------------- I agree with Tim that it is a bit risky to back port this. But I think it is ok to do it as long as it is off by default. So I will go ahead and do that for a 5.13.3 release because it seems there are a few different people requesting this. > 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)