You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@phoenix.apache.org by "James Taylor (JIRA)" <ji...@apache.org> on 2017/06/16 22:35:00 UTC

[jira] [Updated] (PHOENIX-3184) Wrap HBase calls in separate thread to reliably honor query timeout

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

James Taylor updated PHOENIX-3184:
----------------------------------
    Description: If an HBase call stalls, we don't detect and account for this in our query execution time. To solve this, we can wrap any HBase calls that will make an RPC and cancel the thread if our timeout expires. Almost all RPCs are encapsulated in ConnectionQueryServicesImpl.  (was: If an HBase call stalls, we don't detect and account for this in our query execution time. To solve this, we can wrap any HBase calls that will make an RPC and cancel the thread if our timeout expires.)

> Wrap HBase calls in separate thread to reliably honor query timeout
> -------------------------------------------------------------------
>
>                 Key: PHOENIX-3184
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-3184
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: James Taylor
>
> If an HBase call stalls, we don't detect and account for this in our query execution time. To solve this, we can wrap any HBase calls that will make an RPC and cancel the thread if our timeout expires. Almost all RPCs are encapsulated in ConnectionQueryServicesImpl.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)