[
https://issues.apache.org/jira/browse/IMPALA-4773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16674571#comment-16674571
]
bharath v commented on IMPALA-4773:
-----------------------------------
[~tarmstrong] yes.
> 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: Major
> Labels: 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
