jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Egli (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (OAK-2617) Provide config parameter for timing out longrunning/inefficient queries
Date Thu, 12 Mar 2015 13:34:38 GMT

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

Stefan Egli updated OAK-2617:
-----------------------------
    Attachment: OAK-2617.patch

Attached [^OAK-2617.patch] with a suggested implementation.
[~chetanm], [~mreutegg], could you pls have a look? thx!

> Provide config parameter for timing out longrunning/inefficient queries
> -----------------------------------------------------------------------
>
>                 Key: OAK-2617
>                 URL: https://issues.apache.org/jira/browse/OAK-2617
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: mongomk
>    Affects Versions: 1.0.12
>            Reporter: Stefan Egli
>            Assignee: Stefan Egli
>             Fix For: 1.0.13
>
>         Attachments: OAK-2617.patch
>
>
> There have been cases where mongo queries where running for a very long time due to inefficient
use of indexes or wrong indexes - mostly due to resulting traversals of loads of child nodes.
> While a proper fix for this is likely to be found in properly hinting at the right index
(or by not hinting at all and letting mongo decide) - it might nevertheless be a good fallback
plan to let queries not run for an infinite amount of time in case 'something went wrong/inefficient'.
> For that, mongo provides a timeout for queries, see [here|http://mongodb.github.io/node-mongodb-native/driver-articles/anintroductionto1_4_and_2_6.html#maxtimems].
> The suggestion is to make use of this by providing a system property that would set this.
> I'll come up with a patch for this.



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

Mime
View raw message