Re: [Exist-open] Query exceeded predefined output-size-limit (1, 000, 000) for document fragments

[Alberto S. <am...@zb...>]

Hello

Thank you all.
I have a collection with a large number of files that might be causing these shortages.
Bumped the output size limit. Let's see how it handles it.

Thanks

Alberto Simões

On Thursday, March 20th, 2025 at 08:55, Guillaume Mella <gui...@un...> wrote:

> Hello,
>
> Le 19/03/2025 à 16:21, Alberto Simões a écrit :
>
>> Hello
>>
>> I am getting this message: Query exceeded predefined output-size-limit (1,000,000) for document fragments (see below complete log for error).
>>
>> What is the cause, and how can I fix it?
>> Thanks
>
> You are reaching the limit defined in the self documented existdb/etc/conf.xml
>
> <!--
>
> This is the global configuration for the query watchdog. The
>
> watchdog monitors all query processes, and can terminate any
>
> long-running queries if they exceed one of the predefined limits.
>
> These limits are as follows:
>
> - output-size-limit:
>
> this attribute limits the size of XML fragments constructed
>
> using XQuery, and thus sets the maximum amount of main memory a
>
> query is allowed to use. This limit is expressed as the maximum
>
> number of nodes allowed for an in-memory DOM tree. The purpose
>
> of this option is to avoid memory shortages on the server in
>
> cases where users are allowed to run queries that produce very
>
> large output fragments.
>
> - query-timeout:
>
> this attribute sets the maximum amount of time (expressed in
>
> milliseconds) that the query can take before it is killed..
>
> -->
>
> <watchdog
>
> output-size-limit
>
> =
>
> "1000000"
>
> query-timeout
>
> =
>
> "-1"
>
> />
>
> I often increase this value to one order of magnitude. even in the docker instances...
>
> Cheers,
> --
> Guillaume