You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Josh Elser (JIRA)" <ji...@apache.org> on 2017/02/16 21:23:41 UTC
[jira] [Created] (PHOENIX-3684) ConnectionQueryServices connection
leak on principal with "_HOST"
Josh Elser created PHOENIX-3684:
-----------------------------------
Summary: ConnectionQueryServices connection leak on principal with "_HOST"
Key: PHOENIX-3684
URL: https://issues.apache.org/jira/browse/PHOENIX-3684
Project: Phoenix
Issue Type: Bug
Reporter: Arpit Gupta
Assignee: Josh Elser
Priority: Blocker
Fix For: 4.9.1, 4.10.0
Through some internal testing, we found that Ambari's use of Phoenix to host metrics data was leaking ConnectionQueryServices (and thus HConnections and ZK connections), ultimately running into ZK's rate limiting maxClientCnxns.
After a bit of digging around (and revisiting the old issues around this topic PHOENIX-3607, PHOENIX-3611, etc), I finally realized that the logic in ConnectionInfo was simply not correctly handling the {{_HOST}} special string in the principal (that UGI will replace with the FQDN for the current host).
This resulted in Phoenix repeatedly re-logging in the user when they created a new Connection instead of using the UGI current user, leaking another set of connections.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)