[
https://issues.apache.org/jira/browse/IMPALA-6948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dimitris Tsirogiannis resolved IMPALA-6948.
-------------------------------------------
Resolution: Fixed
> Coordinators don't detect the deletion of tables that occurred outside of
> impala after catalog restart
> ------------------------------------------------------------------------------------------------------
>
> Key: IMPALA-6948
> URL: https://issues.apache.org/jira/browse/IMPALA-6948
> Project: IMPALA
> Issue Type: Bug
> Components: Catalog
> Affects Versions: Impala 3.0, Impala 2.12.0
> Reporter: Dimitris Tsirogiannis
> Assignee: Dimitris Tsirogiannis
> Priority: Blocker
> Labels: catalog-server
>
> Upon catalog restart the coordinators detect this event and request a full
> topic update from the statestore. In certain cases, the topic update protocol
> executed between the statestore and the catalog fails to detect catalog
> objects that were deleted from the Metastore externally (e.g. via HIVE), thus
> causing these objects to show up again in each coordinator's catalog cache.
> The end result is that the catalog server and the coordinator's cache are out
> of sync and in some cases the only solution is to restart both the catalog
> and the statestore.
> The following sequence can reproduce this issue:
> {code:java}
> impala> create table lala(int a);
> bash> kill -9 `pidof catalogd`
> hive> drop table lala;
> bash> restart catalogd
> impala> show tables;
> --- lala shows up in the list of tables;{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
