Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 11C41200D3A for ; Tue, 10 Oct 2017 23:22:05 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 108051609CB; Tue, 10 Oct 2017 21:22:05 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 5E4EC160BE1 for ; Tue, 10 Oct 2017 23:22:04 +0200 (CEST) Received: (qmail 82894 invoked by uid 500); 10 Oct 2017 21:22:03 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 82787 invoked by uid 99); 10 Oct 2017 21:22:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Oct 2017 21:22:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id C8E2EC3A44 for ; Tue, 10 Oct 2017 21:22:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id GBwLvN6gPZAt for ; Tue, 10 Oct 2017 21:22:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 7B3DE5F5FD for ; Tue, 10 Oct 2017 21:22:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id B62FBE0F1C for ; Tue, 10 Oct 2017 21:22:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 6D7FC25386 for ; Tue, 10 Oct 2017 21:22:00 +0000 (UTC) Date: Tue, 10 Oct 2017 21:22:00 +0000 (UTC) From: "Mikhail Antonov (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-18786) FileNotFoundException should not be silently handled for primary region replicas MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 10 Oct 2017 21:22:05 -0000 [ https://issues.apache.org/jira/browse/HBASE-18786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16199385#comment-16199385 ] Mikhail Antonov commented on HBASE-18786: ----------------------------------------- [~ghelmling] I kind of remember that about a year ago or so some silent handling for FNFE was added to avoid possible cascading server restarts. Do you remember any more details of it, am I wrong in my recollection? > 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.5.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 (v6.4.14#64029)