[
https://issues.apache.org/jira/browse/HBASE-17095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15666699#comment-15666699
]
Anoop Sam John commented on HBASE-17095:
----------------------------------------
We may have to do some general way? Than throw back FNFE and CorruptedHFile
exception, an exception which will cause the op fully fail? Ya ScannerReset
exception means on the same scanner no hope with retry but a fresh trial after
creating new scanner might help(Like region is moved to other RS by this time).
May be the down layer which actually see CorruptedHFile exception itself has
to make the new Exception type , wrapping the original one? FNFE is in case
of MOB where the ref cell resolve to some path but u r not able to find it.
Correct?
> 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)
