[
https://issues.apache.org/jira/browse/PHOENIX-7470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17930757#comment-17930757
]
Istvan Toth commented on PHOENIX-7470:
--------------------------------------
On further examination, we don't need to use a Configuration object at all.
We are doing a big song and dance to put the principal and keytab into the
configuration, and the reference them, but we can use the strings directly.
> 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)
