[
https://issues.apache.org/jira/browse/FLINK-2224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14586147#comment-14586147
]
Ufuk Celebi commented on FLINK-2224:
------------------------------------
Yes, I agree. Access to JM logs is currently easier via the web interface as
well.
I've looked in to the JM and the respective Akka message is JobStatusChanged (l
287). The error cause contains the root cause as well, but only the exception
message is printed. It's an easy fix and I vote to include it into the release.
If you haven't looked into this yet, I can do the fix.
> JobManager log does not contain root cause and stack trace of exceptions
> ------------------------------------------------------------------------
>
> Key: FLINK-2224
> URL: https://issues.apache.org/jira/browse/FLINK-2224
> Project: Flink
> Issue Type: Bug
> Components: Core
> Reporter: Till Rohrmann
>
> While running cluster tests with failing jobs I noticed that the JobManager
> log file does neither contain the root cause of the failure nor a stack trace
> of it. The error was not sufficient resources available for scheduling.
> For the purpose of debugging, it is crucial to have this information in the
> log file.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
