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 Wed, 16 May 2012 05:48:16 GMT

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

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

wap.w.close() internally will check writer is not equal to nul or not if it is not equal to
null then it will try to close. So here it wont attempt to close the already closed writer.
                
> 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
>            Reporter: Chinna Rao Lalam
>            Assignee: Chinna Rao Lalam
>         Attachments: HBASE-6002.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