[
https://issues.apache.org/jira/browse/HBASE-16017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15357470#comment-15357470
]
Jonathan Hsieh commented on HBASE-16017:
----------------------------------------
Hey guys, I ran into this in trunk and patched it yesterday. I found this
when I started backporting to branch-1. I'm going to address the review over
there. The one major addition over there was a unit test which spurred the
need for a small error semantics change.
Was there a reason why this was only ported to branch-1?
> HBase TableOutputFormat has connection leak in getRecordWriter
> --------------------------------------------------------------
>
> Key: HBASE-16017
> URL: https://issues.apache.org/jira/browse/HBASE-16017
> Project: HBase
> Issue Type: Bug
> Reporter: Zhan Zhang
> Assignee: Zhan Zhang
> Fix For: 2.0.0, 1.4.0
>
> Attachments: HBASE-16017-1.patch
>
>
> Currently getRecordWriter will not release the connection until jvm
> terminate, which is not a right assumption given that the function may be
> invoked many times in the same jvm lifecycle. Inside of mapreduce, the issue
> has already fixed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
