[jira] [Created] (IMPALA-11868) Annotate the Java thread name with query_id during planning

["Joe McDonnell (Jira)" <ji...@apache.org>]

Joe McDonnell created IMPALA-11868:
--------------------------------------

             Summary: Annotate the Java thread name with query_id during planning
                 Key: IMPALA-11868
                 URL: https://issues.apache.org/jira/browse/IMPALA-11868
             Project: IMPALA
          Issue Type: Improvement
          Components: Frontend
    Affects Versions: Impala 4.3.0
            Reporter: Joe McDonnell


Some pieces of catalog code have been using the ThreadNameAnnotator to modify the Java thread name at runtime. This greatly improves the information available via jstacks. For example:
{noformat}
"Thread-543 [invalidating metadata - 579/647 dbs complete]" #1447 prio=5 os_prio=0 tid=0x0000000010f57800 nid=0x75fd runnable [0x00007fe4d265f000]{noformat}
We should do something similar for queries that call into Java frontend code (e.g. during planning). It would be useful to know the query_id for threads when looking at a jstack output.

The main priority would be locations where a thread could spend significant time or get blocked. The most obvious example is during planning:

[https://github.com/apache/impala/blob/master/fe/src/main/java/org/apache/impala/service/Frontend.java#L1730]

[https://github.com/apache/impala/blob/master/fe/src/main/java/org/apache/impala/util/ThreadNameAnnotator.java]

 



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