You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2018/12/14 00:38:04 UTC
[jira] [Commented] (HBASE-18786) FileNotFoundException should not
be silently handled for primary region replicas
[ https://issues.apache.org/jira/browse/HBASE-18786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16720756#comment-16720756 ]
Hudson commented on HBASE-18786:
--------------------------------
SUCCESS: Integrated in Jenkins build HBase-1.3-IT #509 (See [https://builds.apache.org/job/HBase-1.3-IT/509/])
HBASE-18786 FileNotFoundException should not be silently handled for (apurtell: rev b442a7fc92763fb63ed1c01ef4072c9823836d79)
* (delete) hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestCorruptedRegionStoreFile.java
* (delete) hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestRegionServerAbort.java
* (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java
> FileNotFoundException should not be silently handled for primary region replicas
> --------------------------------------------------------------------------------
>
> Key: HBASE-18786
> URL: https://issues.apache.org/jira/browse/HBASE-18786
> Project: HBase
> Issue Type: Sub-task
> Components: regionserver, Scanners
> Reporter: Ashu Pachauri
> Assignee: Andrew Purtell
> Priority: Major
> Fix For: 1.4.0, 1.3.3, 2.0.0
>
> Attachments: HBASE-18786-branch-1.3.patch, HBASE-18786-branch-1.patch, HBASE-18786-branch-1.patch, HBASE-18786.patch, HBASE-18786.patch
>
>
> This is a follow up for HBASE-18186.
> FileNotFoundException while scanning from a primary region replica can be indicative of a more severe problem. Handling them silently can cause many underlying issues go undetected. We should either
> 1. Hard fail the regionserver if there is a FNFE on a primary region replica, OR
> 2. Report these exceptions as some region / server level metric so that these can be proactively investigated.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)