[PHOENIX-3891] ConnectionQueryServices leak on auto-Kerberos-login without REALM in URL

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 4.11.0
• Assignee: Josh Elser
• Reporter: Josh Elser
• Created: 26/May/17 16:26
• Updated: 31/May/17 23:22
• Resolved: 31/May/17 21:38

Description

PHOENIX-3189 fixed some logic in construction of a ConnectionInfo to, when requested by the user, perform the Kerberos login and then construct and cache the ConnectionInfo->ConnectionQueryServices pair.

This approach only works when the principal that the user provides in the JDBC url is exactly what UGI returns as the short name. Logically equivalent principals will result in re-logging in each time and leaking ConnectionQueryService instances (and thus HConnection and ZooKeeper objects).

For example, with Kerberos principals there is a default realm which is implied by krb5.conf when not explicitly provided. Thus: elserj and elserj@APACHE would be considered logically equivalent (when the default realm is "APACHE"). We should expand the isSameName check in ConnectionInfo to be a bit smarter.

Issue Links

• is related to: PHOENIX-3189 HBase/ZooKeeper connection leaks when providing principal/keytab in JDBC url