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 "Zhi Tang (Jira)" <ji...@apache.org> on 2023/10/24 13:39:00 UTC
[jira] [Comment Edited] (IMPALA-12513) The metadata should be reset when the CatalogD become active
[ https://issues.apache.org/jira/browse/IMPALA-12513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17779086#comment-17779086 ]
Zhi Tang edited comment on IMPALA-12513 at 10/24/23 1:38 PM:
-------------------------------------------------------------
CC [~wzhou] There are two cases that trigger a failover of the CatalogD:
①Active CatalogD failure;
②Restart the StatestoreD;
When switching active CatalogD, the loaded metadata in the candidate CatalogD may not be the latest. We should reset the metadata to ensure that there are no metadata inconsistency exceptions after switching.
was (Author: tangzhi):
There are two cases that trigger a failover of the CatalogD:
①Active CatalogD failure;
②Restart the StatestoreD;
When switching active CatalogD, the loaded metadata in the candidate CatalogD may not be the latest. We should reset the metadata to ensure that there are no metadata inconsistency exceptions after switching.
> The metadata should be reset when the CatalogD become active
> ------------------------------------------------------------
>
> Key: IMPALA-12513
> URL: https://issues.apache.org/jira/browse/IMPALA-12513
> Project: IMPALA
> Issue Type: Bug
> Reporter: Zhi Tang
> Priority: Major
>
> When performing an automatic failover of CatalogD, we should ensure that the metadata for active Catalogd is up to date.
--
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