You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tez.apache.org by "Rajesh Balamohan (JIRA)" <ji...@apache.org> on 2016/03/02 03:45:18 UTC
[jira] [Created] (TEZ-3154) Debuggability : Add an option to take
threaddump from a specific vertex/task
Rajesh Balamohan created TEZ-3154:
-------------------------------------
Summary: Debuggability : Add an option to take threaddump from a specific vertex/task
Key: TEZ-3154
URL: https://issues.apache.org/jira/browse/TEZ-3154
Project: Apache Tez
Issue Type: Improvement
Reporter: Rajesh Balamohan
tez.task-specific.launch.cmd-opts and tez.task-specific.launch.cmd-opts.list (e.g "Map 1[10]", 10th task in map 1) options are available to add certain parameters to task specific command line options. It has been useful for launching profilers on specific tasks.
There are scenarios in which taking threaddumps on periodic basis on specific tasks could be helpfule. E.g
- In certain clusters it could be difficult to add profilers.
- There could be scenarios where the tasks are slow due apps using Tez (but the counters might indicate no issues in Tez). (e.g Parsing using SimpleDateFormat for every record could be time consuming)
- In certain clusters, access might not be there to take threaddumps of tasks from NM. YARN's threadstack (in RM UI) is mainly for NM and doesn't work on task level.
Creating this ticket to explore the possibility of adding thread-dump on periodic basis for specific tasks.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)