[
https://issues.apache.org/jira/browse/SLING-7169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16377213#comment-16377213
]
Valentin Olteanu commented on SLING-7169:
-----------------------------------------
I've committed a working patch in
[PR#7|https://github.com/apache/sling-org-apache-sling-testing-clients/pull/7],
which introduces the
[IndexingClient|https://github.com/volteanu/sling-org-apache-sling-testing-clients/blob/SLING-7169/src/main/java/org/apache/sling/testing/clients/indexing/IndexingClient.java].
I've tried the patch by:
1. pause the async index lange
2. start {IndexingClient#waitForAsyncIndexing()}
3. wait 20s to see if the method returns (should not)
4. resume the lane
5. the method returns after a few seconds
6. repeat for the fulltextasync lane
Note that the patch is based on SLING-7509 and SLING-7511.
The only thing I'm not sure about is whether the queries will always pick the
right index (are they specific enough?). Will need [~tmueller] advice for this.
In total, a call to {{#waitForAsyncIndexing()}} will potentially:
* create index definitions under {{/tmp/test/waitForAsyncIndexing/oak:index}}
* create nodes under {{/tmp/test/waitForAsyncIndexing/content}}
* install a bundle with a jsp exposed as a resource in {{/apps/testQuery}}
* create a node {{/content/testquery}} with the previously created resourceType
* run queries via the previously created resource
[~rombert], do you see any issues with this procedure in the context of 0DT? I
want to have this tool working in all the cases.
> 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)
