hadoop-common-issues mailing list archives

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

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

Virag Kothari commented on HADOOP-8661:
---------------------------------------

@Bobby, Just realized while fixing OOZIE-946 that the column storing error message is Blob
and not varchar. So the issue is not as severe as I thought was. Sorry for missing this earlier.
                
> 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
>         Attachments: HADOOP-8661.txt, HADOOP-8661.txt
>
>
> 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