jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Reutegger (JIRA)" <j...@apache.org>
Subject [jira] Closed: (JCR-177) Commit volatile index to disc after some configurable idle time
Date Tue, 09 Aug 2005 08:50:37 GMT
     [ http://issues.apache.org/jira/browse/JCR-177?page=all ]
Marcel Reutegger closed JCR-177:

> 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
>     Assignee: 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:
For more information on JIRA, see:

View raw message