[IMPALA-6254] Track fragment instance id for general purpose threads

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Impala 2.10.0
• Component/s: Backend
• Labels: observability
• Epic Link: Improve Hang Diagnostics
• Epic Color: ghx-label-7
• Assignee: Zoltán Borók-Nagy
• Reporter: Lars Volker
• Created: 28/Nov/17 19:44
• Updated: 31/May/21 16:16
• Resolved: 31/May/21 16:16

Description

Fragment instance threads currently have the instance name in their thread name.

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)

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.

Sub-Tasks

• Extend Thread::Create to track fragment instance id automatically based on parent's fid: Resolved
• Extend various thread pools to track fragment instance id: Resolved