Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 199CAD31D for ; Fri, 24 May 2013 03:23:26 +0000 (UTC) Received: (qmail 56486 invoked by uid 500); 24 May 2013 03:23:26 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 55911 invoked by uid 500); 24 May 2013 03:23:24 -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 55815 invoked by uid 99); 24 May 2013 03:23:21 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 24 May 2013 03:23:21 +0000 Date: Fri, 24 May 2013 03:23:21 +0000 (UTC) From: "Jimmy Xiang (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HBASE-8606) Meta scanner is not closed MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-8606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-8606: ------------------------------- Attachment: trunk-8606_v2.patch Added v2, to put those closes in a try-catch block so as not to leak anything. > Meta scanner is not closed > -------------------------- > > Key: HBASE-8606 > URL: https://issues.apache.org/jira/browse/HBASE-8606 > Project: HBase > Issue Type: Bug > Components: Scanners > Reporter: Jimmy Xiang > Assignee: Jimmy Xiang > Priority: Trivial > Attachments: trunk-8606.patch, trunk-8606_v2.patch > > > In my meta region server log file, I see lots of error messages complaining about meta region scanner lease expired. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira