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

Hadoop QA commented on HBASE-7515:
----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12563908/7515-v5.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
                        Please justify why no new tests are needed for this 
patch.
                        Also please list what manual steps were performed to 
verify this patch.

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: 
https://builds.apache.org/job/PreCommit-HBASE-Build/3945//console

This message is automatically generated.
                
> 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, 7515-v3.txt, 7515-v4.txt, 
> 7515-v5.patch
>
>
> 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

Reply via email to