[
https://issues.apache.org/jira/browse/GEODE-7037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dick Cavender closed GEODE-7037.
--------------------------------
> MAX_QUERY_EXECUTION_TIME is incorrectly shown in docs
> -----------------------------------------------------
>
> Key: GEODE-7037
> URL: https://issues.apache.org/jira/browse/GEODE-7037
> Project: Geode
> Issue Type: Bug
> Components: docs
> Reporter: Dave Barnes
> Assignee: Dave Barnes
> Priority: Minor
> Fix For: 1.10.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Link:
> [https://geode.apache.org/docs/guide/19/developing/query_additional/query_timeout.html]
> Text:
> _"Timeouts for Long-Running Queries
> GemFire can monitor and throw an exception when a query runs longer than a
> configured amount of time. This feature is enabled by setting the
> critical-heap-percentage attribute which detects that the JVM has too little
> heap memory.
> The default query timeout is five hours. Set a different amount of time, in
> milliseconds, by specifying the system variable
> *gemfire.cache.MAX_QUERY_EXECUTION_TIME*. A value of -1 explicitly disables
> the timeout.
> When enabled, a query that runs longer than the configured timeout will be
> cancelled such that it does not finish, and GemFire throws a
> QueryExecutionTimeoutException."_
> The above is wrong. The parameter is case sensitive and it should be:
> *gemfire.Cache.MAX_QUERY_EXECUTION_TIME* with an upper case C.
> This was tested and checked in the code:
> _public static int MAX_QUERY_EXECUTION_TIME =
> Integer.getInteger(DistributionConfig.GEMFIRE_PREFIX +
> "Cache.MAX_QUERY_EXECUTION_TIME", -1);
> _
> So using *gemfire.cache.MAX_QUERY_EXECUTION_TIME* will not change the time
> out.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
