[
https://issues.apache.org/jira/browse/AMQ-6292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15284629#comment-15284629
]
Gary Tully commented on AMQ-6292:
---------------------------------
Acks would already be synced to disk so it makes sense to do a sync at some
stage after the move unless the appender is closed at some stage to force a
sync.
Maybe a sync trace command when a the last ack is appended.{code}
store(new KahaTraceCommand().setMessage("Ack compaction complete " + new
Date()));{code}
> ACK rewrite task does unnecessary syncs
> ---------------------------------------
>
> Key: AMQ-6292
> URL: https://issues.apache.org/jira/browse/AMQ-6292
> Project: ActiveMQ
> Issue Type: Improvement
> Components: KahaDB
> Affects Versions: 5.13.3
> Reporter: Timothy Bish
> Assignee: Timothy Bish
> Fix For: 5.14.0, 5.13.4
>
>
> When rewriting acks from an older journal to a new one the rewrite task
> forces a disk sync on each ack written, should instead just queue the write
> and allow the batch write to sync when it is full or the appender is closed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
