[
https://issues.apache.org/jira/browse/OAK-5978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15940365#comment-15940365
]
Thomas Mueller commented on OAK-5978:
-------------------------------------
See also
http://jackrabbit.apache.org/oak/docs/query/query-engine.html#Slow_Queries_and_Read_Limits
(for LimitReads and LimitInMemory) and
http://jackrabbit.apache.org/oak/docs/query/query-engine.html#Query_Options
(for QueryEngineSettings.failTraversal)
> Allow deployers to configure a query time limit
> -----------------------------------------------
>
> Key: OAK-5978
> URL: https://issues.apache.org/jira/browse/OAK-5978
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: query
> Affects Versions: 1.6.1
> Reporter: Ian Boston
>
> Currently when a query takes a long time to complete, Oak allows it to
> continue to completion, which can under certain circumstances result in
> resource exhaustion and slow performance for all operations depending on Oak.
> This feature request is to apply a deployer configurable time limit to all
> queries. If the query exceeds that time limit, it is canceled with a suitable
> exception, so that it consumes no more resources and the code or user that
> submitted the query is notified.
> Ideally this needs to work while the query is executing inside Oak rather
> than waiting to return via the Oak API before being canceled. Cancelation
> should result in minimal resource usage.
> At this stage, this is an idea. It may not be possible to implement.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
