You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Ufuk Celebi (JIRA)" <ji...@apache.org> on 2015/06/15 17:25:01 UTC

[jira] [Resolved] (FLINK-2224) JobManager log does not contain root cause and stack trace of exceptions

     [ https://issues.apache.org/jira/browse/FLINK-2224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ufuk Celebi resolved FLINK-2224.
--------------------------------
       Resolution: Fixed
    Fix Version/s: master
                   0.9

Fixed via c4f3f48 (release-0.9), b14ec17 (master)

> 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
>             Fix For: 0.9, master
>
>
> 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)