You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Chinmay Kulkarni (Jira)" <ji...@apache.org> on 2020/04/21 00:29:00 UTC
[jira] [Resolved] (PHOENIX-4521) Allow Pherf scenario to define per
query max allowed query execution duration after which thread is
interrupted
[ https://issues.apache.org/jira/browse/PHOENIX-4521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chinmay Kulkarni resolved PHOENIX-4521.
---------------------------------------
Resolution: Fixed
> Allow Pherf scenario to define per query max allowed query execution duration after which thread is interrupted
> ---------------------------------------------------------------------------------------------------------------
>
> Key: PHOENIX-4521
> URL: https://issues.apache.org/jira/browse/PHOENIX-4521
> Project: Phoenix
> Issue Type: Improvement
> Reporter: James R. Taylor
> Assignee: Christine Feng
> Priority: Major
> Labels: phoenix-hardening
> Attachments: PHOENIX-4521.4.x.v1.patch, PHOENIX-4521.4.x.v2.patch, PHOENIX-4521.master.v1.patch, PHOENIX-4521.master.v2.patch, PHOENIX-4521.master.v2.patch, PHOENIX-4521.master.v3.patch, PHOENIX-4521.master.v4.patch, PHOENIX-4521.master.v5.patch, PHOENIX-4521.master.v6.patch, PHOENIX-4521.master.v7.patch
>
> Time Spent: 12h 50m
> Remaining Estimate: 0h
>
> Some clients interrupt the client thread if it doesn't complete in a required amount of time. It would be good if Pherf supported setting this up so we mimic client behavior more closely, as we're theorizing this may be causing some issues.
>
> PLAN
> # Make necessary changes so new timeoutDuration property is recognized and parsed correctly from the scenario .xml file (completed)
> # Implement a per-query, per-iteration timeout
> # Write ITs and UTs
--
This message was sent by Atlassian Jira
(v8.3.4#803005)