[jira] [Resolved] (IMPALA-12060) statestore should only allow a single catalog instance to be part of cluster

["Wenzhe Zhou (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IMPALA-12060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Wenzhe Zhou resolved IMPALA-12060.
----------------------------------
    Fix Version/s: Impala 4.3.0
       Resolution: Duplicate

The issue was fixed by IMPALA-12155.

> statestore should only allow a single catalog instance to be part of cluster
> ----------------------------------------------------------------------------
>
>                 Key: IMPALA-12060
>                 URL: https://issues.apache.org/jira/browse/IMPALA-12060
>             Project: IMPALA
>          Issue Type: Bug
>            Reporter: Abhishek Rawat
>            Assignee: Wenzhe Zhou
>            Priority: Critical
>             Fix For: Impala 4.3.0
>
>
> Today Impala doesn't support multiple catalogd instances to be part of the cluster. When using external Active Passive HA mechanisms like leader election, it may be possible for multiple catalog replicas to be part of the cluster, in some cases. This is mainly because catalogds have no idea that there are other catalogd instances. One way to address this issue could be for statestore to always ensure that there could only be a single instance of catalogd in the cluster. Coordinator also has a config `catalog_service_host` - both statestore and coordinator should have a consistent view and consider the proper catalogd instance to be part of the cluster.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org