You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Jason Huynh (JIRA)" <ji...@apache.org> on 2016/01/06 19:33:39 UTC
[jira] [Updated] (GEODE-245) QueryMonitor cancellation is being
ignored by query using CompactRangeIndex
[ https://issues.apache.org/jira/browse/GEODE-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason Huynh updated GEODE-245:
------------------------------
Priority: Major (was: Minor)
Description: Currently the compact range index does not make a call to QueryMonitor.isQueryCancelled. This allows queries to continue to run even after they have surpassed the max query execution time (was: Currently this test sets a time it expects queries to get cancelled. Then it populates the regions with what it hopes is enough data to cause a query to take longer then the expected time. As machines get faster or the engine gets optimized, these tests will start to fail (or fail intermittently).
Instead a test hook should be used to put stall the query (for example: sleep(timeout)) This will ensure that the time out is hit. We could also reduce the number of objects created in this test at that point.)
Issue Type: Bug (was: Improvement)
Summary: QueryMonitor cancellation is being ignored by query using CompactRangeIndex (was: Modify QueryMonitorDUnitTest to use test hooks to verify query cancellation)
This was discovered while reviewing the QueryMonitor code. The previous ticket was invalid due to a private test but this issue was identified instead.
> QueryMonitor cancellation is being ignored by query using CompactRangeIndex
> ---------------------------------------------------------------------------
>
> Key: GEODE-245
> URL: https://issues.apache.org/jira/browse/GEODE-245
> Project: Geode
> Issue Type: Bug
> Components: querying
> Reporter: Jason Huynh
> Assignee: Jason Huynh
>
> Currently the compact range index does not make a call to QueryMonitor.isQueryCancelled. This allows queries to continue to run even after they have surpassed the max query execution time
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)