[
https://issues.apache.org/jira/browse/PHOENIX-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13906158#comment-13906158
]
Andrew Purtell commented on PHOENIX-56:
---------------------------------------
bq. Pardon my ignorance, but how do I filter tcpdump to just the sqlline.sh
data?
You can capture everything on the client box during a connection attempt and
filter later when investigating. I recommend Wireshark for the latter.
I suggest this because you are reporting what looks like an environmental issue
with spotty connectivity between the client box and the master:
bq. Oh, Phoenix became reachable for a few hours last night. Then it became
unresponsive again. So it is intermittently reachable. wtf mate?
I wouldn't make too much of being able to ssh in even when having connectivity
issues with the HBase master, the default ports for the latter are high in the
ephemeral range and may be treated differently by routers, network firewalls,
or host firewalls.
Also see my suggestion for looking at host kernel logs on the server side for
evidence.
> 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)
