[ https://issues.apache.org/jira/browse/HBASE-6002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13278023#comment-13278023 ]
Zhihong Yu commented on HBASE-6002: ----------------------------------- As you said above, introducing a closed flag wouldn't improve much. I was thinking about a boolean flag which marks whether close() has been attempted on the writer. This is to avoid extraneous logging of IOE's. > 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