hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chinna Rao Lalam (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-6002) Possible chance of resource leak in HlogSplitter
Date Fri, 18 May 2012 17:47:09 GMT

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

Chinna Rao Lalam commented on HBASE-6002:
-----------------------------------------

@Stack:
yes writersClosed flag is used for not to attempt in finally block if the all writers are
closed successfully.

@Ted:
bq."close previously closed stream has no effect" 
I think previous close successful then it wont take any effect (I am fully not sure) i need
to check this.
                
> Possible chance of resource leak in HlogSplitter
> ------------------------------------------------
>
>                 Key: HBASE-6002
>                 URL: https://issues.apache.org/jira/browse/HBASE-6002
>             Project: HBase
>          Issue Type: Bug
>          Components: wal
>    Affects Versions: 0.94.0, 0.96.0
>            Reporter: Chinna Rao Lalam
>            Assignee: Chinna Rao Lalam
>         Attachments: HBASE-6002.patch, HBASE-6002_0.94_1.patch, HBASE-6002_trunk.patch
>
>
> In HLogSplitter.splitLogFileToTemp-Reader(in) is not closed and in finally block in loop
while closing the writers(wap.w) if any exception comes other writers won't close.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message