Uploaded image for project: 'Geode'
  1. Geode
  2. GEODE-7037

MAX_QUERY_EXECUTION_TIME is incorrectly shown in docs

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.10.0
    • Component/s: docs
    • Labels:
      None

      Description

      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.
       

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                dbarnes97 Dave Barnes
                Reporter:
                dbarnes97 Dave Barnes
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 20m
                  20m