[
https://issues.apache.org/jira/browse/HBASE-6002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13287237#comment-13287237
]
Hudson commented on HBASE-6002:
-------------------------------
Integrated in HBase-0.92-security #109 (See
[https://builds.apache.org/job/HBase-0.92-security/109/])
HBASE-6050 HLogSplitter renaming recovered.edits and CJ removing the parent
directory races, making the HBCK to think cluster is inconsistent. and a small
addendum for HBASE-6002 (Ram) (Revision 1342935)
HBASE-6002 Possible chance of resource leak in HlogSplitter (Chinna Rao)
(Revision 1342932)
Result = SUCCESS
ramkrishna :
Files :
*
/hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/regionserver/wal/HLogSplitter.java
ramkrishna :
Files :
*
/hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/regionserver/wal/HLogSplitter.java
> 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
> Fix For: 0.92.2, 0.96.0, 0.94.1
>
> Attachments: HBASE-6002.patch, HBASE-6002_0.92_1.patch,
> HBASE-6002_0.94_1.patch, HBASE-6002_0.94_1.patch, HBASE-6002_trunk.patch,
> HBASE-6002_trunk_1.patch, HBASE-6002_trunk_2.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
