[
https://issues.apache.org/jira/browse/PHOENIX-4489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16336970#comment-16336970
]
Hudson commented on PHOENIX-4489:
---------------------------------
FAILURE: Integrated in Jenkins build Phoenix-master #1919 (See
[https://builds.apache.org/job/Phoenix-master/1919/])
PHOENIX-4489 HBase Connection leak in Phoenix MR Jobs (karanmehta93: rev
65f91a11d1bc2cc4d798ced121f47200bf0fc36c)
* (edit)
phoenix-core/src/main/java/org/apache/phoenix/mapreduce/PhoenixInputFormat.java
> HBase Connection leak in Phoenix MR Jobs
> ----------------------------------------
>
> Key: PHOENIX-4489
> URL: https://issues.apache.org/jira/browse/PHOENIX-4489
> Project: Phoenix
> Issue Type: Bug
> Reporter: Karan Mehta
> Assignee: Karan Mehta
> Priority: Major
> Attachments: PHOENIX-4489.001.patch, PHOENIX-4489.002.patch
>
>
> Phoenix MR jobs uses a custom class {{PhoenixInputFormat}} to determine the
> splits and the parallelism of the work. The class directly opens up a HBase
> connection, which is not closed after the usage. Independently running MR
> jobs should not have any concern, however jobs that run through Phoenix-Spark
> can cause leak issues if this is left unclosed (since those jobs run as a
> part of same JVM).
> Apart from this, the connection should be instantiated with
> {{HBaseFactoryProvider.getHConnectionFactory()}} instead of the default one.
> It can be useful if a separate client is trying to run jobs and wants to
> provide a custom implementation of {{HConnection}}.
> [~jmahonin] Any ideas?
> [~jamestaylor] [~vincentpoon] Any concerns around this?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
