[
https://issues.apache.org/jira/browse/PHOENIX-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13906136#comment-13906136
]
Jeffrey Zhong commented on PHOENIX-56:
--------------------------------------
[~russell.jurney] It will help a lot if you can set log4j correctly in order
for us to see know why getMaster failed.
There maybe no blocking call. The code HBaseAdmin(Configuration) calls
getMaster() in a retry loop(by default is retry 10 times) while getMaster
internally does another retry loop(by default is 10 retries). So totally there
will be 100 times retry and it could last two hours+.
> 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
> Attachments: hbase-site.xml, hbase.dump, sqlline.jstack
>
>
> 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)
