hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-18786) FileNotFoundException should not be silently handled for primary region replicas
Date Fri, 06 Oct 2017 19:25:03 GMT

    [ https://issues.apache.org/jira/browse/HBASE-18786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16195083#comment-16195083
] 

Hudson commented on HBASE-18786:
--------------------------------

Results for branch HBASE-18467, done in 4 hr 24 min and counting
	[build #136 on builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-18467/136/]:
FAILURE
----
details (if available):

(x) *{color:red}-1 overall{color}*
    Committer, please check your recent inclusion of a patch for this issue.

(x) {color:red}-1 general checks{color}
-- For more information [see general report|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-18467/136//General_Nightly_Build_Report/]










(/) {color:green}+1 jdk8 checks{color}
-- For more information [see jdk8 report|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-18467/136//JDK8_Nightly_Build_Report/]


(x) {color:red}-1 source release artifact{color}
-- See build output for details.



> 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
>             Fix For: 2.0.0, 3.0.0, 1.4.0, 1.3.2, 1.5.0
>
>         Attachments: 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
(v6.4.14#64029)

Mime
View raw message