jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Mueller (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-5237) Change default query limit configuration
Date Tue, 13 Dec 2016 13:05:58 GMT

    [ https://issues.apache.org/jira/browse/OAK-5237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15745121#comment-15745121
] 

Thomas Mueller commented on OAK-5237:
-------------------------------------

[~alexander.klimetschek] yes there is some overlap, both this issue and OAK-4888 try to prevent
unexpected behavior (out-of-memory, very slow queries). But OAK-4888 is only ensures an index
is used. When an index is used, OAK-4888 doesn't bark. But even with an index, queries can
be slow, or run out of memory. For example queries that read many nodes (from an index), or
sort by an unindexed column (that is, just use an index for filtering), and so on. This issue
complements OAK-4888 by ensuring a query doesn't eat up too many resources. Query limits are
a basic monitoring and intervention system.

> Change default query limit configuration
> ----------------------------------------
>
>                 Key: OAK-5237
>                 URL: https://issues.apache.org/jira/browse/OAK-5237
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: query
>            Reporter: Thomas Mueller
>            Assignee: Thomas Mueller
>             Fix For: 1.6
>
>
> By default, queries can read an unlimited number of nodes, and an unlimited number of
entries in memory (for "order by" and "union").
> I would like to change the default settings to:
> {noformat}
> -Doak.queryLimitInMemory=500000
> -Doak.queryLimitReads=100000
> {noformat}



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

Mime
View raw message