hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sandy Ryza (JIRA)" <j...@apache.org>
Subject [jira] [Created] (YARN-366) Add a tracing async dispatcher to simplify debugging
Date Wed, 30 Jan 2013 23:57:13 GMT
Sandy Ryza created YARN-366:

             Summary: Add a tracing async dispatcher to simplify debugging
                 Key: YARN-366
                 URL: https://issues.apache.org/jira/browse/YARN-366
             Project: Hadoop YARN
          Issue Type: New Feature
          Components: nodemanager, resourcemanager
    Affects Versions: 2.0.2-alpha
            Reporter: Sandy Ryza
            Assignee: Sandy Ryza

Exceptions thrown in YARN/MR code with asynchronous event handling do not contain informative
stack traces, as all handle() methods sit directly under the dispatcher thread's loop.

This makes errors very difficult to debug for those who are not intimately familiar with the
code, as it is difficult to see which chain of events caused a particular outcome.

I propose adding an AsyncDispatcher that instruments events with tracing information.  Whenever
an event is dispatched during the handling of another event, the dispatcher would annotate
that event with a pointer to its parent.  When the dispatcher catches an exception, it could
reconstruct a "stack" trace of the chain of events that led to it, and be able to log something

This would be an experimental feature, off by default, unless extensive testing showed that
it did not have a significant performance impact.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message