[
https://issues.apache.org/jira/browse/IMPALA-6254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoltán Borók-Nagy resolved IMPALA-6254.
---------------------------------------
Resolution: Fixed
> Track fragment instance id for general purpose threads
> ------------------------------------------------------
>
> Key: IMPALA-6254
> URL: https://issues.apache.org/jira/browse/IMPALA-6254
> Project: IMPALA
> Issue Type: Improvement
> Components: Backend
> Affects Versions: Impala 2.10.0
> Reporter: Lars Volker
> Assignee: Zoltán Borók-Nagy
> Priority: Major
> Labels: observability
>
> Fragment instance threads currently have the instance name in their thread
> name.
> {noformat}
> exec-finstance (finst:1546b532c445c5f3:5dc794e500000003)
> scanner-thread (finst:1546b532c445c5f3:5dc794e500000003, plan-node-id:0,
> thread-idx:0)
> scanner-thread (finst:1546b532c445c5f3:5dc794e500000003, plan-node-id:0,
> thread-idx:1)
> profile-report (finst:1546b532c445c5f3:5dc794e500000003)
> scanner-thread (finst:1546b532c445c5f3:5dc794e500000003, plan-node-id:0,
> thread-idx:2)
> profile-report (finst:1546b532c445c5f3:5dc794e500000000)
> exec-finstance (finst:1546b532c445c5f3:5dc794e500000000)
> {noformat}
> For thread pools that do work that can be tied to particular fragment
> instances, we should look into ways to annotate them. This could require
> adding some breadcrumbs to each instance-specific work item (I/O requests
> etc) so that the worker threads can annotate themselves.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
