You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "nabarun (JIRA)" <ji...@apache.org> on 2018/04/02 20:36:00 UTC

[jira] [Resolved] (GEODE-4867) Query execution time expiration must stop all query execution

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

nabarun resolved GEODE-4867.
----------------------------
       Resolution: Fixed
    Fix Version/s: 1.6.0

> Query execution time expiration must stop all query execution
> -------------------------------------------------------------
>
>                 Key: GEODE-4867
>                 URL: https://issues.apache.org/jira/browse/GEODE-4867
>             Project: Geode
>          Issue Type: Bug
>          Components: querying
>            Reporter: nabarun
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.6.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> *+Current behavior+* :
> When the query execution time expires in the QueryMonitor, the isCancelled boolean is set. But  this is used in only once in the executeQueryOnRemoteAndLocalNodes in DefaultQuery but this is checked at the end after the entire query is executed.
> This results in entire query being executed even though the time for query execution had expired.
> *+Solution+* :
> The time expiration flag needs to be checked in a similar fashion as isLowMemory, which is checked in nearly every step of execution of the query hence the query is stopped when the execution time had expired.
> [no checks needed in the index module]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)