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

Robert Joseph Evans commented on HADOOP-8661:
---------------------------------------------

Glad to see OOZIE-946.  Virag, is it OK for us to drop the severity on 
HADOOP-8661 given OOZIE-946?

I did read through HADOOP-6686 and the reason for including the entire stack 
trace is to improve debugging, which is obviously something we want.  Most 
exceptions do not have a complete stack trace in their message though.  That is 
what getStackTrace() is for.

I have spent a little time to write some code that can parse the stack trace 
and insert it back into the generated exception. I think this is the cleaner 
way to get the debugging, and keep the generated massage almost identical to 
the original message.  I wanted to know what others thought about the 
suggestion. I am fine with dropping it if OOZIE-946 is sufficient. I need some 
time to clean up the code a bit and add some more tests to be sure everything 
works OK even in error cases, but I don't want to spend much time on it if this 
is going to be contentious.

                
> 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

        

Reply via email to