[jira] [Commented] (IMPALA-11731) Consider avoiding table locks from blocking the catalog-update-gathering-thread when the catalog server's catalog_topic_mode is minimal.

["zhi tang (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IMPALA-11731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17636996#comment-17636996 ] 

zhi tang commented on IMPALA-11731:
-----------------------------------

This idea is similar to the one described in https://issues.apache.org/jira/browse/IMPALA-9062, but it was closed. We should be able to find a way to avoid the problems we worry about

> Consider avoiding table locks from blocking the catalog-update-gathering-thread when the catalog server's catalog_topic_mode is minimal.
> ----------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: IMPALA-11731
>                 URL: https://issues.apache.org/jira/browse/IMPALA-11731
>             Project: IMPALA
>          Issue Type: Improvement
>            Reporter: zhi tang
>            Priority: Major
>
> If catalog_topic_mode is minimal, for table updates, catalogd only propagates the database name, table name and catalog version associated with the table. After the update thread acquire the table lock, the catalog-update-gathering-thread can notify the coordinator that the table metadata has changed, rather than waiting for the table lock to be acquired.
> We do not expect the catalog-update-gathering-thread to be blocked because it will block other unrelated updates, such as the problem described in IMPALA-6671. It is necessary to deal with this problem in a more effective way.



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