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 "Sourabh Goyal (Jira)" <ji...@apache.org> on 2021/07/22 12:14:00 UTC
[jira] [Commented] (IMPALA-10817) Share metastoreHmsDDL lock b/w
CatalogOpExecutor and Catalog metastore server
[ https://issues.apache.org/jira/browse/IMPALA-10817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17385452#comment-17385452 ]
Sourabh Goyal commented on IMPALA-10817:
----------------------------------------
Patch for review: https://gerrit.cloudera.org/c/17713/
> Share metastoreHmsDDL lock b/w CatalogOpExecutor and Catalog metastore server
> -----------------------------------------------------------------------------
>
> Key: IMPALA-10817
> URL: https://issues.apache.org/jira/browse/IMPALA-10817
> Project: IMPALA
> Issue Type: Improvement
> Components: Catalog
> Reporter: Sourabh Goyal
> Priority: Major
>
> Currently, when doing create/drop table/db from catalogD, catalogOpExecutor (via Impala Shell) and metastore server (via HS2) acquires lock on their own respective lock objects to prevent concurrent create/drop operations in HMS. But that does not prevent these concurrent operations across CatalogOpExecutor and Metastore server. For example currently a user can perform create/drop HMS operation from Impala shell and catalog metastore server concurrently which is not the desired behavior
--
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