hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Duo Zhang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-17489) ClientScanner may send a next request to a RegionScanner which has been exhausted
Date Fri, 05 May 2017 01:30:04 GMT

    [ https://issues.apache.org/jira/browse/HBASE-17489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15997701#comment-15997701

Duo Zhang commented on HBASE-17489:

Yeah in the hbase client we only use the scanner id when opening scanner since when calling
next or close you need to send the scanner id to RS so you must have known the scanner id

Mind openning a issue for this? I think it is easy to fix. We need to add some comments and
also a UT to confirm that we do not remove it again in the future.


> ClientScanner may send a next request to a RegionScanner which has been exhausted
> ---------------------------------------------------------------------------------
>                 Key: HBASE-17489
>                 URL: https://issues.apache.org/jira/browse/HBASE-17489
>             Project: HBase
>          Issue Type: Bug
>          Components: Client, scan
>    Affects Versions: 2.0.0, 1.3.0, 1.4.0
>            Reporter: Duo Zhang
>            Assignee: Duo Zhang
>            Priority: Critical
>             Fix For: 2.0.0, 1.4.0, 1.3.1
>         Attachments: HBASE-17489-branch-1.3.patch, HBASE-17489-branch-1.patch, HBASE-17489.patch,
HBASE-17489-v1.patch, HBASE-17489-v2.patch, HBASE-17489-v3.patch, HBASE-17489-v4.patch, HBASE-17489-v4.patch,
HBASE-17489-v5.patch, HBASE-17489-v6.patch
> Found it when implementing HBASE-17045. Seems the final result of the scan is correct
but no doubt the logic is broken. We need to fix it to stop things get worse in the future.

This message was sent by Atlassian JIRA

View raw message