[
https://issues.apache.org/jira/browse/HADOOP-8661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13431281#comment-13431281
]
Suresh Srinivas commented on HADOOP-8661:
-----------------------------------------
Echoing what Jason said, it is a good idea to handle this in Oozie. Making an
assumption about the length of exception message and expecting that it would
not change in upstream project is not a good idea.
That said, we could change the message back to shorter length given the thrown
exception has been set with initCause() from where the stack trace can be
derived.
> 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
