[ 
https://issues.apache.org/jira/browse/IMPALA-7450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16773658#comment-16773658
 ] 

ASF subversion and git services commented on IMPALA-7450:
---------------------------------------------------------

Commit 540278d57f9d44917c47ea070169c084cdf6dd61 in impala's branch 
refs/heads/master from Todd Lipcon
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=540278d ]

IMPALA-7450. Set thread name during refresh/load operations

This adds a small utility class for annotating the current thread's name
during potentially long-running operations such as refresh/load. With
this change, jstack output now includes useful thread names like:

During startup:
  "main [invalidating metadata - 128/428 dbs complete]"

While loading a fresh table:
  "pool-4-thread-12 [Loading metadata for: foo_db.foo_table] [Loading
   metadata for all partition(s) of foo_db.foo_table]"

Pool refreshing metadata for a particular path:
  "pool-23-thread-5 [Refreshing file metadata for path:
   hdfs://nameservice1/path/to/partdir..."

Tests: Verified the patch manually by jstacking a catalogd while performing
some workload. Also added a simple unit test to verify the thread renaming
behavior.

Change-Id: Ic7c850d6bb2eedc375ee567c19eb17add335f60c
Reviewed-on: http://gerrit.cloudera.org:8080/11228
Reviewed-by: Bharath Vissapragada <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>


> catalogd should use thread names to make jstack more readable
> -------------------------------------------------------------
>
>                 Key: IMPALA-7450
>                 URL: https://issues.apache.org/jira/browse/IMPALA-7450
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Catalog
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>            Priority: Major
>              Labels: supportability
>
> Currently when long refresh or DDL operations are being processed, it's hard 
> to understand what's going on when looking at a jstack. We should have such 
> potentially-long-running operations temporarily modify the current thread's 
> name to indicate what action is being taken so we can debug more easily.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to