flink-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-949) ChannelManager startup exception not reported in TaskManager
Date Thu, 19 Jun 2014 08:10:24 GMT

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

ASF GitHub Bot commented on FLINK-949:
--------------------------------------

GitHub user uce opened a pull request:

    https://github.com/apache/incubator-flink/pull/28

    [FLINK-949] Properly report GlobalBufferPool OutOfMemoryError to TaskManager

    This is [FLINK-949](https://issues.apache.org/jira/browse/FLINK-949).
    
    Travis seems to have problems with downloading dependencies from Maven central and hence
the [builds fail/timeout](https://travis-ci.org/uce/incubator-flink/builds/27917216).

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/uce/incubator-flink FLINK-949

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-flink/pull/28.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #28
    
----
commit be9f132ec538fba72f9f80cb7aaadf67d845504a
Author: uce <u.celebi@fu-berlin.de>
Date:   2014-06-19T00:42:03Z

    [FLINK-949] Properly report GlobalBufferPool OutOfMemoryError to TaskManager

----


> ChannelManager startup exception not reported in TaskManager
> ------------------------------------------------------------
>
>                 Key: FLINK-949
>                 URL: https://issues.apache.org/jira/browse/FLINK-949
>             Project: Flink
>          Issue Type: Bug
>    Affects Versions: pre-apache-0.5.1
>            Reporter: Ufuk Celebi
>            Assignee: Ufuk Celebi
>
> While debugging a problem with [~rmetzger], we noticded that exception in the constructor
of the {{ChannelManager}} are not properly forwarded to the {{TaskManager}}.
> The concrete problem was the following: num network buffers was misconfigured and tried
to allocate more memory than available on the machine. The respective exception was hiden
in the stdout file instead of the log.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message