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] [Updated] (HBASE-17489) ClientScanner may send a next request to a RegionScanner which has been exhausted
Date Sun, 22 Jan 2017 09:00:34 GMT

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

Duo Zhang updated HBASE-17489:
------------------------------
      Resolution: Fixed
    Hadoop Flags: Reviewed
          Status: Resolved  (was: Patch Available)

Pushed to branch-1.3+. Thanks all for reviewing.

> 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