[
https://issues.apache.org/jira/browse/PHOENIX-4521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17035841#comment-17035841
]
Christine Feng commented on PHOENIX-4521:
-----------------------------------------
[~larsh] Wanted to get your opinion on this; the description is a bit vague. I
interpreted a few ways:
* While executing the queries associated with a single table in a scenario, we
want to interrupt execution once a certain duration is reached (i.e., enforcing
a timeout on total duration during query execution stage)
* Each query associated with a particular table should get a certain amount of
time to execute, after which it will be interrupted (i.e., enforcing a
per-query timeout)
* If TABLE_A has a defined timeout of 500 ms, any query involving TABLE_A
should be interrupted after 500 ms
Do you have any insight on what this Jira is asking for? Thanks in advance.
> Allow Pherf scenario to define per table max allowed query 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
>
> 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 timeout based on each table's timeoutDuration
> ** Timeout each individual job? Loading schema, executing queries, etc.
> ** General timeout for all jobs?
> # Test
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
