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

Posted to issues-all@impala.apache.org by "Wenzhe Zhou (Jira)" <ji...@apache.org> on 2024/03/01 18:33:00 UTC

[jira] [Resolved] (IMPALA-12833) Enabled starting flag 'catalogd_ha_reset_metadata_on_failover' by default

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

Wenzhe Zhou resolved IMPALA-12833.
----------------------------------
    Fix Version/s: Impala 4.4.0
       Resolution: Fixed

> Enabled starting flag 'catalogd_ha_reset_metadata_on_failover' by default
> -------------------------------------------------------------------------
>
>                 Key: IMPALA-12833
>                 URL: https://issues.apache.org/jira/browse/IMPALA-12833
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Backend
>            Reporter: Wenzhe Zhou
>            Assignee: Wenzhe Zhou
>            Priority: Major
>             Fix For: Impala 4.4.0
>
>
> In the abnormal state, table is loaded in coordinator but unloaded in the new active catalogd after catalogd failover. This lead coordinator to use the stale metadata and produce wrong results or encounter query failures. New active catalogd should reset metadata when it becomes active.



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