[
https://issues.apache.org/jira/browse/TEZ-4344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
László Bodor updated TEZ-4344:
------------------------------
Description:
1. set a property of interval of seconds (default: 0 ==> off)
2. attach jstack files to app logs (this is easy maybe, putting jstack log
files next to app syslog files can make it included by yarn)
jstack should have a name like containername_dagname_timestamp
+option if containers should create jstacks even when idle (don't have a task
assigned to them), by default they're not supposed to do so
I don't want to have a jstack dependency for this (configure path, etc.), so an
internal thread dump facility is preferred with zero configuration.
Also this doesn't require new endpoints of AM and task containers (like
TEZ-4345), this can be implemented quite easily.
was:
1. set a property of interval of seconds (default: 0 ==> off)
2. attach jstack files to app logs (this is easy maybe, putting jstack log
files next to app syslog files can make it included by yarn)
jstack should have a name like containername_dagname_timestamp
+option if containers should create jstacks even when idle (don't have a task
assigned to them), by default they're not supposed to do so
I don't want to have a jstack dependency for this (configure path, etc.), so an
internal thread dump facility is preferred with zero configuration.
> Collect jstack periodically from all containers
> -----------------------------------------------
>
> Key: TEZ-4344
> URL: https://issues.apache.org/jira/browse/TEZ-4344
> Project: Apache Tez
> Issue Type: Sub-task
> Reporter: László Bodor
> Priority: Major
>
> 1. set a property of interval of seconds (default: 0 ==> off)
> 2. attach jstack files to app logs (this is easy maybe, putting jstack log
> files next to app syslog files can make it included by yarn)
> jstack should have a name like containername_dagname_timestamp
> +option if containers should create jstacks even when idle (don't have a task
> assigned to them), by default they're not supposed to do so
> I don't want to have a jstack dependency for this (configure path, etc.), so
> an internal thread dump facility is preferred with zero configuration.
> Also this doesn't require new endpoints of AM and task containers (like
> TEZ-4345), this can be implemented quite easily.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
