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 8E53A200D5D for ; Wed, 6 Dec 2017 01:07:12 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 8CF8B160C1C; Wed, 6 Dec 2017 00:07:12 +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 D3C22160C1B for ; Wed, 6 Dec 2017 01:07:11 +0100 (CET) Received: (qmail 47692 invoked by uid 500); 6 Dec 2017 00:07:11 -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 47681 invoked by uid 99); 6 Dec 2017 00:07:11 -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; Wed, 06 Dec 2017 00:07:11 +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 4A25FC4CA7 for ; Wed, 6 Dec 2017 00:07:10 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.011 X-Spam-Level: X-Spam-Status: No, score=-100.011 tagged_above=-999 required=6.31 tests=[SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id XUzoSHfrextj for ; Wed, 6 Dec 2017 00:07:09 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 1FD885F2FE for ; Wed, 6 Dec 2017 00:07:09 +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 BCCE0E25B4 for ; Wed, 6 Dec 2017 00:07:01 +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 B7A9B255C8 for ; Wed, 6 Dec 2017 00:07:00 +0000 (UTC) Date: Wed, 6 Dec 2017 00:07:00 +0000 (UTC) From: "Ted Yu (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-19435) Reopen Files for ClosedChannelException in BucketCache MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 06 Dec 2017 00:07:12 -0000 [ https://issues.apache.org/jira/browse/HBASE-19435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16279413#comment-16279413 ] Ted Yu commented on HBASE-19435: -------------------------------- refreshFileConnection() is called immediately following the error. Could there be a scenario where successive reopening keeps failing ? In that case, performance would continue to suffer. > Reopen Files for ClosedChannelException in BucketCache > ------------------------------------------------------ > > Key: HBASE-19435 > URL: https://issues.apache.org/jira/browse/HBASE-19435 > Project: HBase > Issue Type: Bug > Components: BucketCache > Affects Versions: 2.0.0, 1.3.1 > Reporter: Zach York > Assignee: Zach York > Attachments: HBASE-19435.master.001.patch > > > When using the FileIOEngine for BucketCache, the cache will be disabled if the connection is interrupted or closed. HBase will then get ClosedChannelExceptions trying to access the file. After 60s, the RS will disable the cache. This causes severe read performance degradation for workloads that rely on this cache. FileIOEngine never tries to reopen the connection. This JIRA is to reopen files when the BucketCache encounters a ClosedChannelException. -- This message was sent by Atlassian JIRA (v6.4.14#64029)