[jira] [Updated] (IMPALA-12305) Impala server hanging when processing DDL if CatalogD HA is enabled

["Abhishek Rawat (Jira)" <ji...@apache.org>]

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

Abhishek Rawat updated IMPALA-12305:
------------------------------------
    Priority: Critical  (was: Major)

> Impala server hanging when processing DDL if CatalogD HA is enabled 
> --------------------------------------------------------------------
>
>                 Key: IMPALA-12305
>                 URL: https://issues.apache.org/jira/browse/IMPALA-12305
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Backend, Frontend
>    Affects Versions: Impala 4.3.0
>            Reporter: Wenzhe Zhou
>            Assignee: Wenzhe Zhou
>            Priority: Critical
>             Fix For: Impala 4.3.0
>
>
> In IMPALA-12286, catalogd re-generate its Catalog Service ID in JniCatalog when it becomes active. But CatalogServiceCatalog is not updated when new Catalog Service ID is generated. This causes coordinator hanging when processing DDLs.
> In CatalogServer class, member variable is_active_ is not protected by mutex catalog_lock_, and pending_topic_updates_ is not cleared when the catalogd becomes active. It's possible catalog server sends pending catalog topic updates with old Catalog Service ID then sends catalog topic updates with new Catalog Service ID.



--
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