You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Julian Reschke (JIRA)" <ji...@apache.org> on 2015/12/22 14:27:46 UTC

[jira] [Updated] (OAK-3822) DocumentStore query API should allow specifying a timeout for queries

     [ https://issues.apache.org/jira/browse/OAK-3822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Julian Reschke updated OAK-3822:
--------------------------------
    Summary: DocumentStore query API should allow specifying a timeout for queries  (was: DocumentStore query API should allow specifying a timeout)

> DocumentStore query API should allow specifying a timeout for queries
> ---------------------------------------------------------------------
>
>                 Key: OAK-3822
>                 URL: https://issues.apache.org/jira/browse/OAK-3822
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: documentmk
>            Reporter: Julian Reschke
>            Priority: Minor
>
> There are cases where a query should be terminated instead of running to completion. In one particular case, we see {{ClusterNodeInfoDocument.all()}} needing 15 minutes (!) on an Oracle database. In the context of this call, this essentially means the server is burning.
> The API should allow setting a max. acceptable time for the query to complete, after which it should be terminated. With that, we could at least fail fast.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)