[
https://issues.apache.org/jira/browse/JCR-3162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13170132#comment-13170132
]
Marcel Reutegger commented on JCR-3162:
---------------------------------------
I also noticed that the test is not included in the TestAll suite of the
respective package. This means the new test is not run with every build.
The new test uses annotations to mark the test, which makes it difficult to use
in the TestAll. Is there a specific reason why you used annotations instead of
inheriting from JUnitTest.
I quickly extended the test to make the test nodes versionable and check
consistency on the complete workspace (including the version storage). Running
the test now results in random failure for me.
See attached patch.
> 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
> Fix For: 2.3.6
>
> Attachments: DbClusterTestJCR3162.patch, JCR-3162-v2.patch,
> JCR-3162-v3.patch, JCR-3162-v4.patch, JCR-3162-v5.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
