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 "Sai Hemanth Gantasala (Jira)" <ji...@apache.org> on 2023/01/26 19:48:00 UTC

[jira] [Resolved] (IMPALA-11808) Improve catalogD cache performance in a multi service environment for a refresh/invalidate query

     [ https://issues.apache.org/jira/browse/IMPALA-11808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sai Hemanth Gantasala resolved IMPALA-11808.
--------------------------------------------
    Resolution: Fixed

Resolving this Jira as the patch has been merged to master branch. 

> Improve catalogD cache performance in a multi service environment for a refresh/invalidate query
> ------------------------------------------------------------------------------------------------
>
>                 Key: IMPALA-11808
>                 URL: https://issues.apache.org/jira/browse/IMPALA-11808
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Catalog
>            Reporter: Sai Hemanth Gantasala
>            Assignee: Sai Hemanth Gantasala
>            Priority: Major
>
> Improve catalogD cache performance in a multi-service environment for a refresh/invalidate query.
> This patch supports a new event called reload event in catalogD. This event is used to update table/file metadata for a refresh or invalidate command in other replicas of catalogDs when one of the replicas issues a refresh/invalidate command. HIVE-26838 is the Hive jira that adds support for this reload event. This feature is disabled by default using a config enable_reload_events. To use this feature set this config to true and impala will be able to fire reload events. The processing of reload events in the event processor is always enabled. There is an end-to-end test added for this feature which currently checks the firing/creation of the reload event and self-event check in the event processor. There is also an end-to-end test that tests this reload event in the event processor. 
> There is also a follow-up jira [IMPALA-11822|http://issues.apache.org/jira/browse/IMPALA-11822] to track the optimization patch for this feature.



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