[
https://issues.apache.org/jira/browse/PHOENIX-4521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chinmay Kulkarni updated PHOENIX-4521:
--------------------------------------
Fix Version/s: 5.1.0
> 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
> Affects Versions: 5.0.0, 4.15.0, 4.14.3
> Reporter: James R. Taylor
> Assignee: Christine Feng
> Priority: Major
> Labels: phoenix-hardening
> Fix For: 5.1.0, 4.16.0
>
> 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)
