hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jingcheng Du (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-17095) The ClientSimpleScannr cannot be stopped if the hfile is corrupt or cannot found
Date Tue, 15 Nov 2016 04:39:58 GMT

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

Jingcheng Du updated HBASE-17095:
---------------------------------
    Description: 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.  (was:
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 those exceptions directly
from server and don't retry the scan in the client.)

> The ClientSimpleScannr cannot be stopped 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
>
> 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)

Mime
View raw message