[
https://issues.apache.org/jira/browse/TEZ-3154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajesh Balamohan updated TEZ-3154:
----------------------------------
Description:
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.
High level e.g: "--hiveconf tez.task-specific.launch.cmd-opts="
-DthreadDumpInterval=5 " --hiveconf tez.task-specific.launch.cmd-opts.list="Map
1[10,15]" - This should print thread-dumps in tasks 10, 15 in Map-1 every 5
seconds.
was:
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.
> 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.
> High level e.g: "--hiveconf tez.task-specific.launch.cmd-opts="
> -DthreadDumpInterval=5 " --hiveconf
> tez.task-specific.launch.cmd-opts.list="Map 1[10,15]" - This should print
> thread-dumps in tasks 10, 15 in Map-1 every 5 seconds.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
