You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Christopher L. Shannon (JIRA)" <ji...@apache.org> on 2016/07/27 19:03:20 UTC
[jira] [Resolved] (AMQ-6377) Introduce a periodic disk sync mode
for KahaDB journal
[ https://issues.apache.org/jira/browse/AMQ-6377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christopher L. Shannon resolved AMQ-6377.
-----------------------------------------
Resolution: Fixed
Fix Version/s: 5.14.0
[~gtully], Patch is committed and seems to work well in my testing. Take a look and let me know if you think anything should be tweaked.
It's set up so that an fsync will be done for the current data file (if necessary) at the set interval time, when the current file is rotated, and also if the journal is closed.
> Introduce a periodic disk sync mode for KahaDB journal
> ------------------------------------------------------
>
> Key: AMQ-6377
> URL: https://issues.apache.org/jira/browse/AMQ-6377
> Project: ActiveMQ
> Issue Type: New Feature
> Components: Broker, KahaDB
> Affects Versions: 5.13.4
> Reporter: Christopher L. Shannon
> Assignee: Christopher L. Shannon
> Fix For: 5.14.0
>
>
> KahaDB has two modes for journal disk syncs, either always sync for each write or never sync. I'm proposing that we add a third option, a period disk sync.
> The intended behavior of this would be to run a task in the file appender that would sync the file (if necessary) at some periodic interval (such as every 500 ms, or 1 second, etc) instead of every write. The file would also be synced on close (on file rollover or shutdown)
> In my testing, syncing every 1 second has been proven to be nearly indistinguishable performance as never disk syncing but is a safer option as you insure that a sync is performed at least once per interval.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)