You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Michael Smith (Jira)" <ji...@apache.org> on 2026/04/01 22:00:00 UTC
[jira] [Created] (IMPALA-14872) Don't hold query_driver_map_ lock while calling GetMaxBackendStateLagMs
Michael Smith created IMPALA-14872:
--------------------------------------
Summary: Don't hold query_driver_map_ lock while calling GetMaxBackendStateLagMs
Key: IMPALA-14872
URL: https://issues.apache.org/jira/browse/IMPALA-14872
Project: IMPALA
Issue Type: Bug
Affects Versions: Impala 4.5.0
Reporter: Michael Smith
query_driver_map_ is a highly contended data structure. Accessing it acquires a lock that prevents any other query progress on queries that share a shard, and by default there are only 4 shards.
GetMaxBackendStateLagMs acquires a lock on each BackendState object, which may also be in use (notably while sending a CancelQueryFInstancesRequestPB RPC in Cancel()), for a coordinator within DoFuncForAllEntries in https://github.com/apache/impala/blob/4.5.0/be/src/service/impala-server.cc#L2983. Let's stop doing that.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)