Mailing-List: contact jackrabbit-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jackrabbit-dev@incubator.apache.org
Message-ID: <2126282559.1123575695217.JavaMail.jira@ajax.apache.org>
Date: Tue, 9 Aug 2005 10:21:35 +0200 (CEST)
From: "Marcel Reutegger (JIRA)" <jira@apache.org>
To: jackrabbit-dev@incubator.apache.org
Subject: [jira] Created: (JCR-177) Commit volatile index to disc after some
 configurable idle time
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Commit volatile index to disc after some configurable idle time
---------------------------------------------------------------

         Key: JCR-177
         URL: http://issues.apache.org/jira/browse/JCR-177
     Project: Jackrabbit
        Type: Improvement
  Components: query  
 Environment: svn revision: 230783
    Reporter: Marcel Reutegger
    Priority: Minor
     Fix For: 1.0


The query handler keeps the most recent part of the index in memory (volatile index). That index is committed to disc when a certain amount of nodes (config param: minMergeDocs) has been added. Most of the times the volatile index will contain some nodes, causing a redo.log that needs to be applied when the jackrabbit process is killed.

In addition to the size threshold (minMergeDocs) of the volatile index, an idle time limit should force a commit to disc. The volatile index would be written to disc after some configurable idle time. This will result in an persistent index (on dic) which is most of the time in sync with the data, but still minimizes the disc IO during heavy modification activity on the workspace.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira