sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vikas Saurabh (JIRA)" <>
Subject [jira] [Commented] (SLING-8407) JobManagerImpl.findJobs should prevent traversal
Date Fri, 10 May 2019 16:21:00 GMT


Vikas Saurabh commented on SLING-8407:

[~marett], option traversal fail is a loose hint to pak to fail fast if the best available
option is to traverse. It's akin to Index hints in usual parlance (well oak supports real
index hint using option index tag... )

Going towards this new behavior using a configuration is already something that [~egli] proposed
and [~tmueller] updated his patch accordingly.

> JobManagerImpl.findJobs should prevent traversal
> ------------------------------------------------
>                 Key: SLING-8407
>                 URL:
>             Project: Sling
>          Issue Type: Improvement
>          Components: Event
>            Reporter: Thomas Mueller
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
> The method [JobManagerImpl.findJobs|]
runs a JCR query to find all jobs for a topic.
> It is possible that such a query is running while the repository isn't initialized yet,
meaning while the index isn't available yet. What is happening in this case is that the query
is traversing all nodes below that path, triggering a warning that the query doesn't use an
index. It is sometimes happening when a health check is running before the repository is initialized
(ReplicationQueueHealthCheck and DistributionQueueHealthCheck).
> It doesn't make sense that the query traverses the nodes. It should use an index. If
the index isn't available yet, it should fail. Therefore, the query should use "option(traversal
fail)". That would result in an exception that can be caught.  I will log a related issue
to change the health checks to process this exception and return HEALTH_CHECK_ERROR for this

This message was sent by Atlassian JIRA

View raw message