Mailing-List: contact issues-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Wed, 27 Jul 2016 13:40:21 +0000 (UTC)
From: "Christopher L. Shannon (JIRA)" <jira@apache.org>
To: issues@activemq.apache.org
Message-ID: <JIRA.12992928.1469626799000.146608.1469626821054@Atlassian.JIRA>
In-Reply-To: <JIRA.12992928.1469626799000@Atlassian.JIRA>
References: <JIRA.12992928.1469626799000@Atlassian.JIRA> <JIRA.12992928.1469626799028@arcas>
Subject: [jira] [Created] (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: Wed, 27 Jul 2016 13:40:22 -0000

Christopher L. Shannon created AMQ-6377:
-------------------------------------------

             Summary: 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: Bug
          Components: Broker, KahaDB
    Affects Versions: 5.13.4
            Reporter: Christopher L. Shannon
            Assignee: Christopher L. Shannon


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)