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

Posted to issues@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2019/07/24 18:48:00 UTC

[jira] [Updated] (HBASE-22715) All scan requests should be handled by scan handler threads in RWQueueRpcExecutor

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

Andrew Purtell updated HBASE-22715:
-----------------------------------
    Summary: All scan requests should be handled by scan handler threads in RWQueueRpcExecutor  (was: All scan requests should be handled by scan handler threads)

> All scan requests should be handled by scan handler threads in RWQueueRpcExecutor
> ---------------------------------------------------------------------------------
>
>                 Key: HBASE-22715
>                 URL: https://issues.apache.org/jira/browse/HBASE-22715
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 1.4.10
>            Reporter: Jeongdae Kim
>            Assignee: Jeongdae Kim
>            Priority: Minor
>
> When we use RWQueueRpcExecutor, all scans should be handled by scan handler threads, not read handler.
>  
> Before HBASE-17508, when calling openScanner() in client, a region server doesn't make results, just open scanner and return scanner id. So, this request(open) is executed in read handlers intentionally.
>   
> However, since HBASE-17508,, actual scan behavior happened while opening a scanner,
> I think this request should probably be executed in scan handlers when using RWQueueRpcExecutor.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)