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

Posted to issues@phoenix.apache.org by "Jaanai (JIRA)" <ji...@apache.org> on 2018/09/30 03:03:00 UTC

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

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

Jaanai commented on PHOENIX-4936:
---------------------------------

For massive data table, running a full scan might cause RS down or completely fills the queue of RPC hander.
I think we should throw an exception when hits 'hbase.rpc.timeout ',  because the scan requests are not canceled on the server side, the users will not realize has done what shouldn't they do and they will try run this full scan query again if an empty result is silently returned.
Actually,  we should forbid users to launch a full scan query which will be a significant effect for stability.

> 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)