phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christine Feng (Jira)" <j...@apache.org>
Subject [jira] [Updated] (PHOENIX-4521) Allow Pherf scenario to define per table max allowed query duration after which thread is interrupted
Date Mon, 10 Feb 2020 22:44:00 GMT

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

Christine Feng updated PHOENIX-4521:
------------------------------------
    Description: 
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
 # Implement a timeout based on each table's timeoutDuration
 ** Timeout each individual job? Loading schema, executing queries, etc.
 ** General timeout for all jobs?

  was: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.


> 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
>  # Implement a timeout based on each table's timeoutDuration
>  ** Timeout each individual job? Loading schema, executing queries, etc.
>  ** General timeout for all jobs?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message