Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 8 Jan 2013 21:24:13 +0000 (UTC)
From: "Jean-Daniel Cryans (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12626440.1357605780502.99468.1357680253324@arcas>
In-Reply-To: <JIRA.12626440.1357605780502@arcas>
References: <JIRA.12626440.1357605780502@arcas>
Subject: [jira] [Commented] (HBASE-7515) Store.loadStoreFiles should close
 opened files if there's an exception
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jean-Daniel Cryans commented on HBASE-7515:
-------------------------------------------

bq. How about this one ?

The store file that threw the exception might still be opened, for example in HBASE-7513 it opens fine but the exception is thrown in another part of the code. You might also be overwriting {{ioe}}.
                
> Store.loadStoreFiles should close opened files if there's an exception
> ----------------------------------------------------------------------
>
>                 Key: HBASE-7515
>                 URL: https://issues.apache.org/jira/browse/HBASE-7515
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.94.3
>            Reporter: Jean-Daniel Cryans
>            Assignee: Ted Yu
>             Fix For: 0.96.0, 0.94.5
>
>         Attachments: 7515.txt, 7515-v2.txt
>
>
> Related to HBASE-7513. If a RS is able to open a few store files in {{Store.loadStoreFiles}} but one of them fails like in 7513, the opened files won't be closed and file descriptors will remain in a CLOSED_WAIT state.
> The situation we encountered is that over the weekend one region was bounced between >100 region servers and eventually they all started dying on "Too many open files".

--
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