[
https://issues.apache.org/jira/browse/PHOENIX-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13903536#comment-13903536
]
Lars Hofhansl commented on PHOENIX-56:
--------------------------------------
Nothing. It just holds client resources (region cache, etc) that would go away
when the JVM exits. It's more important to close open scanners, but even those
are removed at the server when their lease expires (after 1 minute by default).
A Phoenix client only needs to hold a single HConnection, right?
Let's see if we can reproduce this in the office tomorrow, might just be a
simple memory leak lurking somewhere.
> Phoenix/JDBC becomes unresponsive
> ---------------------------------
>
> Key: PHOENIX-56
> URL: https://issues.apache.org/jira/browse/PHOENIX-56
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 2.2.3
> Environment: HBase 0.94.6
> Reporter: Russell Jurney
>
> After some hours or days, our Phoenix JDBC connection becomes unresponsive.
> It can't be reached unless we remove all tables, including SYSTEM.TABLE and
> restart HBase.
> There are no errors that accompany this problem, so we don't know how to
> debug it. Is anyone else seeing this behavior?
> Using a different client version of the JAR does result in an error saying
> version mismatch... so at some level we think the service is running. It just
> can't complete a connection. sqlline.sh freezes when we connect.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
