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 "Vihang Karajgaonkar (Jira)" <ji...@apache.org> on 2021/05/21 23:31:00 UTC
[jira] [Updated] (IMPALA-10502) delayed 'Invalidated objects in
cache' cause 'Table already exists'
[ https://issues.apache.org/jira/browse/IMPALA-10502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vihang Karajgaonkar updated IMPALA-10502:
-----------------------------------------
Priority: Critical (was: Minor)
> delayed 'Invalidated objects in cache' cause 'Table already exists'
> -------------------------------------------------------------------
>
> Key: IMPALA-10502
> URL: https://issues.apache.org/jira/browse/IMPALA-10502
> Project: IMPALA
> Issue Type: Bug
> Components: Catalog, Clients, Frontend
> Affects Versions: Impala 3.4.0
> Reporter: Adriano
> Assignee: Vihang Karajgaonkar
> Priority: Critical
>
> In fast paced environment where the interval between the step 1 and 2 is # < 100ms (a simplified pipeline looks like):
> 0- catalog 'on demand' in use and disableHmsSync (enabled or disabled: no difference)
> 1- open session to coord A -> DROP TABLE X -> close session
> 2- open session to coord A -> CREATE TABLE X-> close session
> Results: the step -2- can fail with table already exist.
> During the internal investigation was discovered that IMPALA-9913 will regress the issue in almost all scenarios.
> However considering that the investigation are internally ongoing it is nice to have the event tracked also here.
> Once we are sure that IMPALA-9913 fix these events we can close this as duplicate, in alternative carry on the investigation.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org