hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Raghu Angadi (JIRA)" <j...@apache.org>
Subject [jira] Issue Comment Edited: (HADOOP-1857) Ability to run a script when a task fails to capture stack traces
Date Thu, 13 Sep 2007 17:30:32 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-1857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12527192
] 

rangadi edited comment on HADOOP-1857 at 9/13/07 10:29 AM:
----------------------------------------------------------------

If it s a C/C++ program, why not print the stacktrace in the signal handler to stderr? Is
stderr shown on webui? With a multithreaded program, stack trace with core may not show the
stacktrace for the offending thread, rather for the last thread that is killed last (at least
on x86 Linux, anyway).


      was (Author: rangadi):
    If it s a C/C++ program, why not print the stacktrace in the signal handler to stderr?
Is stderr shown on webui? With a multithreaded program, stack trace with core may not show
the stacktrace for the offending thread, instread for the last thread that is killed (at least
on x86 Linux, anyway).

  
> Ability to run a script when a task fails to capture stack traces
> -----------------------------------------------------------------
>
>                 Key: HADOOP-1857
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1857
>             Project: Hadoop
>          Issue Type: Improvement
>          Components: mapred
>    Affects Versions: 0.14.0
>            Reporter: Amareshwari Sri Ramadasu
>            Assignee: Amareshwari Sri Ramadasu
>             Fix For: 0.15.0
>
>
> This basically is for providing a better user interface for debugging failed
> jobs. Today we see stack traces for failed tasks on the job ui if the job
> happened to be a Java MR job. For non-Java jobs like Streaming, Pipes, the
> diagnostic info on the job UI is not helpful enough to debug what might have
> gone wrong. They are usually framework traces and not app traces.
> We want to be able to provide a facility, via user-provided scripts, for doing
> post-processing on task logs, input, output, etc. There should be some default
> scripts like running core dumps under gdb for locating illegal instructions,
> the last few lines from stderr, etc.  These outputs could be sent to the
> tasktracker and in turn to the jobtracker which would then display it on the
> job UI on demand.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message