[
https://issues.apache.org/jira/browse/AMQ-6203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15232409#comment-15232409
]
Jeff Genender commented on AMQ-6203:
------------------------------------
Hi Tim, thanks for the quick response. May I ask how is this not applicable to
a point release from the perspective that it has the potential to fix a blocker
bug(s) that affects 3 major versions of ActiveMQ? The code looks good and it
seems that the behavior of this fix is transparent to the user. Its a good fix
that has a great impact and it really would be great to get it into those other
point releases. AMQ-5695 looks heavily connected as we have determined form
log files that it looks like the acks are what cause the log file leaks in
those versions.
> 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)
