You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2009/02/25 14:37:01 UTC
[jira] Created: (JCR-1998) Initialize hierarchy cache on startup
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
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.
[jira] Updated: (JCR-1998) Initialize hierarchy cache on startup
Posted by "Marcel Reutegger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcel Reutegger updated JCR-1998:
----------------------------------
Attachment: JCR-1998.patch
Proposed patch.
> 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
> Attachments: 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.
[jira] Updated: (JCR-1998) Initialize hierarchy cache on startup
Posted by "Marcel Reutegger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcel Reutegger updated JCR-1998:
----------------------------------
Fix Version/s: core 1.4.9
Merged changes into 1.4 branch in revision: 748140
> 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.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.
[jira] Updated: (JCR-1998) Initialize hierarchy cache on startup
Posted by "Marcel Reutegger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcel Reutegger updated JCR-1998:
----------------------------------
Attachment: JCR-1998-2.patch
Proposed patch.
> 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.
[jira] Updated: (JCR-1998) Initialize hierarchy cache on startup
Posted by "Marcel Reutegger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcel Reutegger updated JCR-1998:
----------------------------------
Attachment: (was: JCR-1998-2.patch)
> 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.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.
[jira] Issue Comment Edited: (JCR-1998) Initialize hierarchy cache
on startup
Posted by "Marcel Reutegger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676703#action_12676703 ]
mreutegg edited comment on JCR-1998 at 2/25/09 8:55 AM:
----------------------------------------------------------------
> The default value would be the current behaviour (using background thread)
This is actually wrong.
The cache initialization was introduced in 1.5.0 (JCR-1337), then improved and put into a background thread in current trunk (JCR-1884). Which means it should be the other way around. Default is to *not* run initialization in a background thread.
was (Author: mreutegg):
> The default value would be the current behaviour (using background thread)
This is actually wrong.
The cache initialization was introduced in 1.5.0 (JCR-1337), then improved and put into a background thread in current trunk (JCR-1998). Which means it should be the other way around. Default is to *not* run initialization in a background thread.
> 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
>
> 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.
[jira] Resolved: (JCR-1998) Initialize hierarchy cache on startup
Posted by "Marcel Reutegger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcel Reutegger resolved JCR-1998.
-----------------------------------
Resolution: Fixed
Fix Version/s: 1.6.0
Committed patch in revision: 748066
> 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: 1.6.0
>
> Attachments: 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.
[jira] Reopened: (JCR-1998) Initialize hierarchy cache on startup
Posted by "Marcel Reutegger (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (JCR-1998) Initialize hierarchy cache on startup
Posted by "Marcel Reutegger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676703#action_12676703 ]
Marcel Reutegger commented on JCR-1998:
---------------------------------------
> The default value would be the current behaviour (using background thread)
This is actually wrong.
The cache initialization was introduced in 1.5.0 (JCR-1337), then improved and put into a background thread in current trunk (JCR-1998). Which means it should be the other way around. Default is to *not* run initialization in a background thread.
> 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
>
> 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.
[jira] Commented: (JCR-1998) Initialize hierarchy cache on startup
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12682314#action_12682314 ]
Jukka Zitting commented on JCR-1998:
------------------------------------
Since we already released a version of this in 1.4.9, I'd rather keep this closed and open a new issue for any further changes. We can drop the "1.6.0" tag from this issue if you want to make major changes in trunk.
> 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.
[jira] Resolved: (JCR-1998) Initialize hierarchy cache on startup
Posted by "Marcel Reutegger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcel Reutegger resolved JCR-1998.
-----------------------------------
Resolution: Fixed
> Since we already released a version of this in 1.4.9, I'd rather keep this closed and open a new issue for any further changes.
Make sense. I've created a new issue: JCR-2027.
> 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: 1.6.0, core 1.4.9
>
> Attachments: 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.