phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <>
Subject [jira] [Updated] (PHOENIX-3891) ConnectionQueryServices leak on auto-Kerberos-login without REALM in URL
Date Fri, 26 May 2017 19:18:04 GMT


Josh Elser updated PHOENIX-3891:
    Attachment: PHOENIX-3891.002.patch

.002 Missed removing an unnecessary import.

> ConnectionQueryServices leak on auto-Kerberos-login without REALM in URL
> ------------------------------------------------------------------------
>                 Key: PHOENIX-3891
>                 URL:
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>            Priority: Critical
>             Fix For: 4.11.0
>         Attachments: PHOENIX-3891.001.patch, PHOENIX-3891.002.patch
> 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
> 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.

This message was sent by Atlassian JIRA

View raw message