hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Srinivas (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-8661) Stack Trace in Exception.getMessage causing oozie DB to have issues
Date Wed, 08 Aug 2012 18:35:21 GMT

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

Suresh Srinivas commented on HADOOP-8661:
-----------------------------------------

On 2.0, the stack trace may be a little different, since we have switched to protobuf RPC
engine. This change was done in HADOOP-6686. So any solution needs to consider some of the
discussions from that jira.
                
> Stack Trace in Exception.getMessage causing oozie DB to have issues
> -------------------------------------------------------------------
>
>                 Key: HADOOP-8661
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8661
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: ipc
>    Affects Versions: 0.23.3, 2.0.0-alpha, 3.0.0
>            Reporter: Robert Joseph Evans
>            Assignee: Robert Joseph Evans
>            Priority: Critical
>
> It looks like all exceptions produced by RemoteException include the full stack trace
of the original exception in the message.  This is causing issues for oozie because they store
the message in their database and it is getting very large.  This appears to be a regression
from 1.0 behavior.

--
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

        

Mime
View raw message