[
https://issues.apache.org/jira/browse/OAK-4734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15525436#comment-15525436
]
Marcel Reutegger commented on OAK-4734:
---------------------------------------
I think the failures are caused by a race condition in the test setup. An
initial index is created on ns1 with a first async index run, then property
change and async index update tasks are scheduled on both cluster nodes. It may
happen that the first async index update task run on ns2 does not yet see the
initial index and then tries to initialize it as well.
My proposed fix is to ensure the initial index is visible on ns2 as well before
the tasks are scheduled.
[~alexparvulescu] & [~chetanm] does this invalidate any of test assertions?
> AsyncIndexUpdateClusterTestIT fails occasionally
> ------------------------------------------------
>
> Key: OAK-4734
> URL: https://issues.apache.org/jira/browse/OAK-4734
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core
> Affects Versions: 1.5.9
> Reporter: Marcel Reutegger
> Assignee: Marcel Reutegger
> Priority: Minor
> Fix For: 1.6
>
>
> Seen on travis: https://travis-ci.org/apache/jackrabbit-oak/builds/156735673
> {noformat}
> missingCheckpointDueToEventualConsistency(org.apache.jackrabbit.oak.plugins.index.AsyncIndexUpdateClusterTestIT)
> Time elapsed: 6.159 sec <<< FAILURE!
> java.lang.AssertionError: Reindexing should not happen
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertFalse(Assert.java:64)
> at
> org.apache.jackrabbit.oak.plugins.index.AsyncIndexUpdateClusterTestIT.after(AsyncIndexUpdateClusterTestIT.java:84)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
