[
https://issues.apache.org/jira/browse/SLING-7169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16387556#comment-16387556
]
Valentin Olteanu commented on SLING-7169:
-----------------------------------------
After a few iterations, I've came up with the following algorithm that works on
all the cases (including older sling/oak):
* get configured lanes from {{AsyncIndexerService}} (in sling there's only 1)
* for each lane:
** create an index
** create content specific to that index
** try query with {{option(index tag mytag)}}, if it's not working, drop the
option
** get the plan of the query to make sure it is served by the proper index
** get number of results
** repeat until we get 1 result
There are more details hidden in the patch:
https://github.com/apache/sling-org-apache-sling-testing-clients/pull/7/files
> FullTextIndexingTest sometimes fails with a timeout
> ---------------------------------------------------
>
> Key: SLING-7169
> URL: https://issues.apache.org/jira/browse/SLING-7169
> Project: Sling
> Issue Type: Bug
> Components: Launchpad
> Reporter: Robert Munteanu
> Priority: Major
> Labels: sling-IT
> Attachments: SLING-7169-logs.tar.gz
>
>
> The test fails maybe 1 in 10 runs. I could reproduce this locally by running
> many times. I've also seen it once on Jenkins.
> **Old description below**
> After upgrading the launchpad to commons.threads 3.2.10 the
> FullTextIndexingTest failed ( [build
> 1547|https://builds.apache.org/job/sling-launchpad-testing-1.8/1547/] ).
> I also reproduced it once locally.
> [~kwin] - since the commons.threads release is the potential root cause, can
> you please take a look at the failure and see if it's related?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
