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 "Tim Armstrong (Jira)" <ji...@apache.org> on 2020/01/21 21:04:00 UTC
[jira] [Updated] (IMPALA-4773) Supportability improvements for
IMPALA-4765
[ https://issues.apache.org/jira/browse/IMPALA-4773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tim Armstrong updated IMPALA-4773:
----------------------------------
Priority: Minor (was: Major)
> Supportability improvements for IMPALA-4765
> -------------------------------------------
>
> Key: IMPALA-4773
> URL: https://issues.apache.org/jira/browse/IMPALA-4773
> Project: IMPALA
> Issue Type: Bug
> Components: Catalog
> Affects Versions: Impala 2.8.0
> Reporter: Alexander Behm
> Priority: Minor
> Labels: observability, supportability
>
> The patch for addressing IMPALA-4765 introduced a new critical data structure 'tableLoadingBarrier_' to prevent using multiple table-loading threads for the same table.
> However, the following bug might be difficult to detect with the current logging//metrics. If for some reason an entry in the 'tableLoadingBarrier_' is never removed then that table will never again be loaded and all queries waiting for that table will hang (and will not be cancellable, see IMPALA-915). The only remedy is to restart the catalogd.
> We should carefully consider the above possibility and how to debug/identify it from logs, and perhaps enhance the logging.
--
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