[
https://issues.apache.org/jira/browse/HBASE-17095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15672921#comment-15672921
]
Anoop Sam John edited comment on HBASE-17095 at 11/17/16 6:30 AM:
------------------------------------------------------------------
So we throw back CorruptedHFileException or FNFE back to client now so that we
dont end up throwing ScannerResetException. It will be better if u can create
a new HBase specific exception, extending DNRIOE for the HFile not found case.
Being more generic and checking all possible cases, am ok we can do in another
issue
Else +1
was (Author: anoop.hbase):
So we throw back CorruptedHFileException or FNFE back to client now so that we
dont end up throwing ScannerResetException. It will be better if u can create
a new HBase specific exception, extending DNRIOE for the HFile not found case.
Else +1
> The ClientSimpleScanner keeps retrying if the hfile is corrupt or cannot found
> ------------------------------------------------------------------------------
>
> Key: HBASE-17095
> URL: https://issues.apache.org/jira/browse/HBASE-17095
> Project: HBase
> Issue Type: Bug
> Components: regionserver, scan
> Reporter: Jingcheng Du
> Assignee: Jingcheng Du
> Attachments: HBASE-17095.patch, TestScannerWithCorruptHFile.java
>
>
> In {{RsRPCServices.scan}}, most of IOE are thrown as a
> {{ScannerResetException}}, even when the hfile is corrupt or it cannot be
> found. The {{ClientScannr.loadCache}} will keep retrying when the exception
> is {{ScannerResetException}}. We could throw CorruptHFileException and
> FileNotFoundException directly from server and don't retry the scan in the
> client.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
