You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Istvan Toth (Jira)" <ji...@apache.org> on 2025/02/26 17:01:00 UTC
[jira] [Updated] (PHOENIX-7470) Simplify Kerberos login in ConnectionInfo
[ https://issues.apache.org/jira/browse/PHOENIX-7470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Istvan Toth updated PHOENIX-7470:
---------------------------------
Summary: Simplify Kerberos login in ConnectionInfo (was: Revisit Kerberos login in ConnectionInfo)
> Simplify Kerberos login in ConnectionInfo
> -----------------------------------------
>
> Key: PHOENIX-7470
> URL: https://issues.apache.org/jira/browse/PHOENIX-7470
> Project: Phoenix
> Issue Type: Bug
> Components: core
> Reporter: Istvan Toth
> Priority: Major
>
> Performing Kerberso login in ConnetionInfo causes a performance regression, which is partially fixed by PHOENIX-7646
> We need to check how the kerberos principal is handled in Phoenix.
> I strongly suspect that Phoenix won't handle different principals for different connections in the same JVM. This is not necessarily the problem, but we should minimize the performance cost of Kerberos logins.
> The root of the perf regression is that in order to use the HBase Kerberos utulity functions for custom principlas, we need to update the Configuration object.
> If we do this in the CQSI object, using the cached Configuration object, then the performance cost is negligible.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)