Mailing-List: contact issues-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Mon, 6 Mar 2017 12:57:32 +0000 (UTC)
From: "Christopher L. Shannon (JIRA)" <jira@apache.org>
To: issues@activemq.apache.org
Message-ID: <JIRA.12992928.1469626799000.6323.1488805052958@Atlassian.JIRA>
In-Reply-To: <JIRA.12992928.1469626799000@Atlassian.JIRA>
References: <JIRA.12992928.1469626799000@Atlassian.JIRA> <JIRA.12992928.1469626799028@jira-lw-us.apache.org>
Subject: [jira] [Commented] (AMQ-6377) Introduce a periodic disk sync mode
 for KahaDB journal
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 06 Mar 2017 12:57:37 -0000


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

Christopher L. Shannon commented on AMQ-6377:
---------------------------------------------

[~gtully], I went ahead and fixed this to just do the enum comparison so there is no more use of String in that getter.

> 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.15#6346)