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] Reopened: (JCR-1998) Initialize hierarchy cache on startup
Date Mon, 16 Mar 2009 13:27:50 GMT

     [ https://issues.apache.org/jira/browse/JCR-1998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Marcel Reutegger reopened JCR-1998:
-----------------------------------


Rethinking the initialization in a background thread again, I now come to the conclusion that
it should be initialized either completely on startup or not at all. A background thread puts
additional load on the process, possibly fighting for I/O with other startup procedures.

> Initialize hierarchy cache on startup
> -------------------------------------
>
>                 Key: JCR-1998
>                 URL: https://issues.apache.org/jira/browse/JCR-1998
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-core
>            Reporter: Marcel Reutegger
>            Priority: Minor
>             Fix For: core 1.4.9, 1.6.0
>
>         Attachments: JCR-1998-2.patch, JCR-1998.patch
>
>
> In some cases it may be desirable to initialize the hierarchy cache in the search index
on startup. Currently this initialization is done in the background. For larger workspaces,
this puts considerable load on the repository and may slow down access and queries. There
should be a configuration parameter that forces the repository to initialize the hierarchy
cache on startup and only return the repository instance when the initialization is completed.
 The default value would be the current behaviour (using background thread).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message