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

Posted to issues@hbase.apache.org by "Zach York (JIRA)" <ji...@apache.org> on 2017/02/02 20:51:51 UTC

[jira] [Updated] (HBASE-17587) Do not Rethrow DoNotRetryIOException as UnknownScannerException

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

Zach York updated HBASE-17587:
------------------------------
    Attachment: HBASE-17587.branch-1.3.001.patch

> Do not Rethrow DoNotRetryIOException as UnknownScannerException
> ---------------------------------------------------------------
>
>                 Key: HBASE-17587
>                 URL: https://issues.apache.org/jira/browse/HBASE-17587
>             Project: HBase
>          Issue Type: Bug
>          Components: Coprocessors, regionserver, rpc
>    Affects Versions: 2.0.0, 1.3.0
>            Reporter: Zach York
>            Assignee: Zach York
>             Fix For: 2.0.0, 1.4.0, 1.3.1
>
>         Attachments: HBASE-17587.branch-1.3.001.patch
>
>
> HBase commit https://github.com/apache/hbase/commit/94ade6a514e9935a8c283befb31f29cd8d3a2045 broke co-processors (such as Phoenix) throwing DoNotRetryIOExceptions when scanning a table. This change rethrows them as UnknownScannerExceptions which the HBase client will retry on. This is unintended behavior since co-processors should be able to throw DoNotRetryIOExceptions back to the client. This came up through a phoenix IT when trying to upgrade to HBase 1.3.0 https://github.com/apache/phoenix/pull/230



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)