[jira] [Commented] (PHOENIX-4936) Empty resultset returned when hbase.rpc.timeout hit

["Vincent Poon (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/PHOENIX-4936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16634452#comment-16634452 ] 

Vincent Poon commented on PHOENIX-4936:
---------------------------------------

Been playing around with this, some odd behavior:
If hbase.rpc.timeout is low (in my case <20s), the query throws an OutOfOrderScannerNextException  saying "was there a rpc timeout?"
f hbase.rpc.timeout is say 60-120s , the query returns an empty resultset
If hbase.rpc.timeout is 1200s, the query returns the correct results.

In the hbase.rpc.timeout of 60s case, the query returns after around 5 minutes.
So it seems like maybe there's a bug somewhere during repeated rpc calls, where a later rpc timeout causes an empty resultset.

> Empty resultset returned when hbase.rpc.timeout hit
> ---------------------------------------------------
>
>                 Key: PHOENIX-4936
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4936
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.14.0
>            Reporter: Vincent Poon
>            Priority: Critical
>
> Seeing this on a large syscat table (~11gb)
> From sqlline, issue a SELECT statement which does a full table scan
> hbase.rpc.timeout gets hit, and instead of getting an exception, an empty resultset is silently returned.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)