You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Julien Le Dem (Created) (JIRA)" <ji...@apache.org> on 2012/04/09 00:32:17 UTC
[jira] [Created] (MAPREDUCE-4121) dump the threads stack trace to
stdout before killing a Task in timeout
dump the threads stack trace to stdout before killing a Task in timeout
-----------------------------------------------------------------------
Key: MAPREDUCE-4121
URL: https://issues.apache.org/jira/browse/MAPREDUCE-4121
Project: Hadoop Map/Reduce
Issue Type: Improvement
Reporter: Julien Le Dem
Typically when a job fails because of tasks timing out we investigate the issue by running the job again and triggering a dump of the thread stack traces of one of the tasks with jstack/"kill -3" before it times out.
It would be convenient if the Task tracker could do the same right before killing tasks in time out. This usually points at the offending code.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (MAPREDUCE-4121) dump the threads stack trace to
stdout before killing a Task in timeout
Posted by "Julien Le Dem (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-4121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julien Le Dem resolved MAPREDUCE-4121.
--------------------------------------
Resolution: Duplicate
> dump the threads stack trace to stdout before killing a Task in timeout
> -----------------------------------------------------------------------
>
> Key: MAPREDUCE-4121
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4121
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Reporter: Julien Le Dem
>
> Typically when a job fails because of tasks timing out we investigate the issue by running the job again and triggering a dump of the thread stack traces of one of the tasks with jstack/"kill -3" before it times out.
> It would be convenient if the Task tracker could do the same right before killing tasks in time out. This usually points at the offending code.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4121) dump the threads stack trace to
stdout before killing a Task in timeout
Posted by "Todd Lipcon (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-4121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13249642#comment-13249642 ]
Todd Lipcon commented on MAPREDUCE-4121:
----------------------------------------
Dup of MAPREDUCE-1119?
> dump the threads stack trace to stdout before killing a Task in timeout
> -----------------------------------------------------------------------
>
> Key: MAPREDUCE-4121
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4121
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Reporter: Julien Le Dem
>
> Typically when a job fails because of tasks timing out we investigate the issue by running the job again and triggering a dump of the thread stack traces of one of the tasks with jstack/"kill -3" before it times out.
> It would be convenient if the Task tracker could do the same right before killing tasks in time out. This usually points at the offending code.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4121) dump the threads stack trace to
stdout before killing a Task in timeout
Posted by "Julien Le Dem (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-4121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13249628#comment-13249628 ]
Julien Le Dem commented on MAPREDUCE-4121:
------------------------------------------
I see several ways of doing this.
one is to add a jstack() method to org.apache.hadoop.util.Shell to run jstack (or kill -3) on the command line.
The other one is to use sun.tools.jstack.JStack.main() directly (if the class is present).
These all require the PID of the process to send the signal to.
org.apache.hadoop.mapred.TaskTracker would call jstack() before killing the Task
> dump the threads stack trace to stdout before killing a Task in timeout
> -----------------------------------------------------------------------
>
> Key: MAPREDUCE-4121
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4121
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Reporter: Julien Le Dem
>
> Typically when a job fails because of tasks timing out we investigate the issue by running the job again and triggering a dump of the thread stack traces of one of the tasks with jstack/"kill -3" before it times out.
> It would be convenient if the Task tracker could do the same right before killing tasks in time out. This usually points at the offending code.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4121) dump the threads stack trace to
stdout before killing a Task in timeout
Posted by "Julien Le Dem (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-4121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13249675#comment-13249675 ]
Julien Le Dem commented on MAPREDUCE-4121:
------------------------------------------
Yes it is a duplicate. I did not find it when I opened this one.
Any plan to put it in the 0.20 branch ?
> dump the threads stack trace to stdout before killing a Task in timeout
> -----------------------------------------------------------------------
>
> Key: MAPREDUCE-4121
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4121
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Reporter: Julien Le Dem
>
> Typically when a job fails because of tasks timing out we investigate the issue by running the job again and triggering a dump of the thread stack traces of one of the tasks with jstack/"kill -3" before it times out.
> It would be convenient if the Task tracker could do the same right before killing tasks in time out. This usually points at the offending code.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4121) dump the threads stack trace to
stdout before killing a Task in timeout
Posted by "Todd Lipcon (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-4121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13249681#comment-13249681 ]
Todd Lipcon commented on MAPREDUCE-4121:
----------------------------------------
I don't think anyone is working on it. If you want to provide a backport patch for branch-1 I can take a look -- but I imagine it will be a substantial amount of work -- the code changed a lot since then.
> dump the threads stack trace to stdout before killing a Task in timeout
> -----------------------------------------------------------------------
>
> Key: MAPREDUCE-4121
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4121
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Reporter: Julien Le Dem
>
> Typically when a job fails because of tasks timing out we investigate the issue by running the job again and triggering a dump of the thread stack traces of one of the tasks with jstack/"kill -3" before it times out.
> It would be convenient if the Task tracker could do the same right before killing tasks in time out. This usually points at the offending code.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira