[jira] [Commented] (REEF-1618) Add stack trace to exceptions handled in TaskHostBase

["Mariia Mykhailova (JIRA)" <ji...@apache.org>]

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

Mariia Mykhailova commented on REEF-1618:
-----------------------------------------

Do we also want to show this stack trace in driver log? Currently log would look like this, without stack trace

{noformat}
1416 WARNING: Received IFailedTask with Id: IMRUMaster-1 and message: TaskSystemError from endpoint habr.ru with systemState TasksRunning in retry#: 1.
...
1420 INFO: GetTaskErrorEventByExceptionType: with task id: IMRUMaster-1, exception type Org.Apache.REEF.IMRU.OnREEF.IMRUTasks.IMRUTaskSystemException, innerException type System.NullReferenceException, InnerExceptionMessage Object reference not set to an instance of an object., evaluator id: Node-6-1474933827184
{noformat}


> Add stack trace to exceptions handled in TaskHostBase
> -----------------------------------------------------
>
>                 Key: REEF-1618
>                 URL: https://issues.apache.org/jira/browse/REEF-1618
>             Project: REEF
>          Issue Type: Improvement
>          Components: IMRU, REEF.NET
>            Reporter: Mariia Mykhailova
>            Assignee: Mariia Mykhailova
>            Priority: Minor
>              Labels: FT
>             Fix For: 0.16
>
>
> When user code throws exception, {{TaskHostBase.HandleException}} logs some information about it, but not all, for example, stack trace is missing. On the driver side, we also don't get stack trace. This is extremely inconvenient when troubleshooting an exception, we need to log stack trace at some point. 
> As a fix, I suggest that we log full information about {{originalException}} in {{TaskHostBase.HandleException}} before passing on new exception.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)