You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@phoenix.apache.org by "Lokesh Khurana (Jira)" <ji...@apache.org> on 2025/01/06 23:56:00 UTC

[jira] [Created] (PHOENIX-7502) Decouple principal from HAGroupInfo

Lokesh Khurana created PHOENIX-7502:
---------------------------------------

             Summary: Decouple principal from HAGroupInfo
                 Key: PHOENIX-7502
                 URL: https://issues.apache.org/jira/browse/PHOENIX-7502
             Project: Phoenix
          Issue Type: Improvement
            Reporter: Lokesh Khurana


For Phoenix HA Connections, we maintain a cache of HAGroupInfo to current ClusterRoleRecord of the HA Group. But we are not including principal as part of the [key.|https://github.com/apache/phoenix/blob/91cae2577ca2c1e473995f6b541e1a277628e5b0/phoenix-core-client/src/main/java/org/apache/phoenix/jdbc/HighAvailabilityGroup.java#L833]



This forces us to have a separate group name for each principal leading to separate CRR for each principal, but one CRR per policy for a cluster should be sufficient. 

We should decouple principal from HAGroupInfo, so that clients from different principal can use one CRR.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)