You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Alex Parvulescu (Updated) (JIRA)" <ji...@apache.org> on 2011/12/01 18:36:40 UTC
[jira] [Updated] (JCR-3162) Index update overhead on cluster slave
due to JCR-905
[ https://issues.apache.org/jira/browse/JCR-3162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Parvulescu updated JCR-3162:
---------------------------------
Attachment: JCR-3162-v2.patch
Attaching v2 of the patch.
It is basically v1 + a test + some feature flags.
I managed to find a way to test this problem within JR Core, which should allow us to have some meaningful progress.
The test DbClusterTestJCR3162 contains 2 feature flags (which will be removed once the patch is good):
- JCR3162_ENABLE_CLUSTER_DELETE this is the JCR-905 fix which can be switched on/off with the help of this flag
- JCR3162_ENABLE_REINDEX this controls the new code (reindexing if the index is considered stale)
So basically:
- both flags off: you can see the initial behaviour (pre JCR-905) in action. The test fails (as it should).
- just JCR3162_ENABLE_CLUSTER_DELETE represents the current behaviour of the repository (the test passes)
- just JCR3162_ENABLE_REINDEX represents the patch in action (the test passes!)
The original problem still stands: how do we know if an index is stale or not. Default workspace will be covered, the other workspaces are going to be initializes asynchronously, so there are no guarantees.
> Index update overhead on cluster slave due to JCR-905
> -----------------------------------------------------
>
> Key: JCR-3162
> URL: https://issues.apache.org/jira/browse/JCR-3162
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: clustering
> Reporter: Alex Parvulescu
> Priority: Minor
> Attachments: JCR-3162-v2.patch, JCR-3162.patch
>
>
> JCR-905 is a quick and dirty fix and causes overhead on a cluster slave node when it processes revisions.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira