hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-17489) ClientScanner may send a next request to a RegionScanner which has been exhausted
Date Sun, 22 Jan 2017 14:05:27 GMT

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

Hudson commented on HBASE-17489:
--------------------------------

SUCCESS: Integrated in Jenkins build HBase-1.4 #599 (See [https://builds.apache.org/job/HBase-1.4/599/])
HBASE-17489 ClientScanner may send a next request to a RegionScanner (zhangduo: rev 57409371a063ed4d93292ca6e0b7d5b8866e1ffc)
* (edit) hbase-client/src/main/java/org/apache/hadoop/hbase/client/ReversedClientScanner.java
* (edit) hbase-client/src/main/java/org/apache/hadoop/hbase/client/ClientScanner.java
* (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/RSRpcServices.java
* (edit) hbase-client/src/test/java/org/apache/hadoop/hbase/client/TestClientScanner.java


> 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
(v6.3.4#6332)

Mime
View raw message