[
https://issues.apache.org/jira/browse/PHOENIX-7726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lokesh Khurana updated PHOENIX-7726:
------------------------------------
Description:
When a client queries one cluster for its CRR status, the server needs to know
the role of its peer cluster. If the server cannot connect to the peer's ZK
(ZooKeeper) service, it reports an UNKNOWN role, resulting in an inaccurate CRR
status. This connectivity issue is bidirectional. This Jira specifically
addresses and resolves the logic and error handling to ensure an accurate CRR
status is returned even when ZK connectivity is intermittently lost.
Also fix proper propagation of CRR not found exception back to driver for
proper fallback.
was:When a client queries one cluster for its CRR status, the server needs to
know the role of its peer cluster. If the server cannot connect to the peer's
ZK (ZooKeeper) service, it reports an UNKNOWN role, resulting in an inaccurate
CRR status. This connectivity issue is bidirectional. This Jira specifically
addresses and resolves the logic and error handling to ensure an accurate CRR
status is returned even when ZK connectivity is intermittently lost.
> Handle Unknown Roles scenarios in CRR on Clients coming from servers
> --------------------------------------------------------------------
>
> Key: PHOENIX-7726
> URL: https://issues.apache.org/jira/browse/PHOENIX-7726
> Project: Phoenix
> Issue Type: Sub-task
> Reporter: Lokesh Khurana
> Assignee: Lokesh Khurana
> Priority: Major
>
> When a client queries one cluster for its CRR status, the server needs to
> know the role of its peer cluster. If the server cannot connect to the peer's
> ZK (ZooKeeper) service, it reports an UNKNOWN role, resulting in an
> inaccurate CRR status. This connectivity issue is bidirectional. This Jira
> specifically addresses and resolves the logic and error handling to ensure an
> accurate CRR status is returned even when ZK connectivity is intermittently
> lost.
>
> Also fix proper propagation of CRR not found exception back to driver for
> proper fallback.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
